ansible/ansible

Public scan — anyone with this URL can view this analysis. Sign up to track your own repos privately, run scheduled re-scans, and get AI fix prompts via your dashboard.

119 of your 200 findings came from Repobility's proprietary detections. ✓ Repobility tags below mark them.

Scan timing: clone 6.38s · analysis 21.43s · 15.0 MB · GitHub API rate-limit (preflight)

https://github.com/ansible/ansible · scanned 2026-06-05 08:39 UTC (5 days, 20 hours ago) · 10 languages

1041 raw signals (193 security + 848 graph) 28th percentile · Python · large (100-500K LoC) System graph score 81 (lower by 14)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 5 days, 20 hours ago · v2 · 483 actionable findings from 2 signal sources. 117 repeated signals grouped for readability. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON

100.0% cov · 398 findings

Score breakdown â 2026-05-18-v5

Component	Sub-score	Weight	Contribution
`structure_score`	85.0	0.15	12.75
`security_score`	39.7	0.25	9.93
`testing_score`	100.0	0.20	20.00
`documentation_score`	91.0	0.15	13.65
`practices_score`	42.0	0.15	6.30
`code_quality`	42.0	0.10	4.20
Overall		1.00	66.8

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 23 High 21 Medium 81 Low 194 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 85 System graph 398 Crowd 0 Layer: Quality 316 Security 48 Software 92 Cicd 4 Api 1 Network 21 Frontend 1

Exclude dismissed / FP Exclude test files

Bug-class explainers. Each card groups findings of the same shape — these are the patterns most likely to ship to prod and reappear in future scans unless you systematically fix the cause, not just the instance.

Duplicates & near-duplicates 5 findings

What it is: Same function copy-pasted into multiple modules with minor variations.

Why it matters: Each copy drifts independently — bug fixes apply to one, miss the others.

How AI causes it: AI completes the same pattern in each file rather than refactoring to a shared helper.

Fix approach: Extract the duplicated logic into the most general module both call sites already import. Add tests at the helper level.

5 matching findings on this repo

low Near-duplicate function bodies in 2 places repo-level
low Near-duplicate function bodies in 3 places repo-level
low Near-duplicate function bodies in 5 places
low Near-duplicate function bodies in 6 places
low Near-duplicate function bodies in 4 places

View all duplicates & near-duplicates findings →

Legacy markers 7 findings

What it is: TODO, FIXME, XXX, HACK comments. Often indicate a known-broken path the author meant to fix.

Why it matters: Each marker is an unfinished thought. Production code shouldn't ship with debt that's documented but not tracked.

How AI causes it: AI mirrors the style of the codebase, so existing TODOs propagate into new code.

Fix approach: Convert each into a ticket. Delete the comment when the ticket lands. Use a pre-commit hook to block new TODOs without an issue link.

7 matching findings on this repo

low Old/deprecated-named symbol `cmp_legacy` in test/units/module_utils/facts/hardw…
low Old/deprecated-named symbol `test_legacy` in test/units/utils/test_serializatio…
low Old/deprecated-named symbol `inventory_legacy` in test/integration/targets/inve…
low Old/deprecated-named symbol `read_python_coverage_legacy` in test/lib/ansible_t…
low Old/deprecated-named symbol `inventory_legacy` in lib/ansible/_internal/_json/_…
low Old/deprecated-named symbol `_inventory_legacy` in lib/ansible/cli/inventory.py…
low Old/deprecated-named symbol `_inventory_legacy` in lib/ansible/plugins/inventor…

View all legacy markers findings →

Commented-out code 115 findings

What it is: Lines of source that were intentionally disabled but never deleted.

Why it matters: Git already remembers history — commented code rots, becomes wrong, and adds noise to diffs.

How AI causes it: AI sometimes comments out broken code instead of fixing it. Reviewers approve out of inertia.

Fix approach: Delete. Trust `git log`. If you really need to remember, save it in a notes file under `docs/`.

12 matching findings on this repo

info Commented-code block (7 lines) in test/units/conftest.py:57
info Commented-code block (6 lines) in test/units/_internal/templating/test_jinja_bi…
info Commented-code block (5 lines) in test/units/module_utils/test_distro.py:2
info Commented-code block (5 lines) in test/units/module_utils/common/test_sys_info.…
info Commented-code block (5 lines) in test/units/module_utils/basic/test_selinux.py…
info Commented-code block (5 lines) in test/units/module_utils/basic/test_get_module…
info Commented-code block (5 lines) in test/units/module_utils/basic/test_argument_s…
info Commented-code block (5 lines) in test/units/module_utils/basic/test_platform_d…
info Commented-code block (5 lines) in test/units/module_utils/basic/test__symbolic_…
info Commented-code block (5 lines) in test/units/module_utils/basic/test_dict_conve…
info Commented-code block (5 lines) in test/units/module_utils/basic/test_atomic_mov…
info Commented-code block (5 lines) in test/units/module_utils/basic/test_filesystem…

View all commented-out code findings →

Config drift 7 findings

What it is: Settings duplicated across env files, Docker compose, K8s, and code defaults, all with slightly different values.

Why it matters: Production behaviour depends on whichever copy your loader reads first. Subtle bugs in staging that don't reproduce in dev.

How AI causes it: AI writes new config from memory rather than reading the existing source.

Fix approach: Pick one source of truth (env vars + a settings module). Have every other place import from there. Lint for duplicates in CI.

7 matching findings on this repo

medium No CI/CD configuration found
high Phantom test coverage: test_plugin__init_config_none test/units/plugins/test_plugins.py:88
high Phantom test coverage: test_plugin__init_config_str test/units/plugins/test_plugins.py:85
high Phantom test coverage: test_plugin__init_config_list test/units/plugins/test_plugins.py:81
low File has no detected symbols: test/integration/targets/ansible-config/files/ini…
critical Possible secret in test/integration/targets/ansible-config/tasks/main.yml test/integration/targets/ansible-config/tasks/mai…:102
low Old/deprecated-named symbol `tag_copy` in lib/ansible/config/manager.py:115

View all config drift findings →

For AI agents: Voting guide (TP/FP) MCP manifest Stdio wrapper SARIF Integrate Findings queue Vote TP/FP on findings to calibrate the engine.

For AI agents + API integrations

Email me when this repo regresses

Free. We re-scan periodically; new criticals → your inbox. No signup required for the scan itself.

API access

This page is publicly accessible at: https://repobility.com/scan/529d3d56-8a1c-4035-8414-20e7a8c17bc0/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/529d3d56-8a1c-4035-8414-20e7a8c17bc0/

Important — please don't re-submit the same URL repeatedly. The submission endpoint is idempotent: re-submitting the same git URL returns this same scan_token, not a new one. To re-scan this repo, sign up free and use the dashboard.