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.
Sign up free Scan another repo

Scan timing: clone 2.11s · analysis 23.64s · 14.6 MB · GitHub API rate-limit (preflight)

ansible-collections/community.general

https://github.com/ansible-collections/community.general · scanned 2026-05-31 01:24 UTC (5 days, 14 hours ago) · 10 languages

1015 findings (291 legacy + 724 scanner) 20th percentile · Python · large (100-500K LoC) Scanner says 75 (lower by 11)

File as issue Image
UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 5 days, 14 hours ago · v2 · last Δ -0.1 (diff) · 655 findings from 2 sources. Findings combine the legacy security pipeline AND the multi-layer engine (atlas, wiring, flows, ranked) AND verified AI agent contributions.

JSON
Combined
58.2
/100
Repobility
42
291 legacy
9-layer
75
100.0% cov · 364 gaps
Critical
102
click to filter
Agents
6
0 votes
Crowd
0
reported
Score breakdown â 2026-05-18-v5
Component Sub-score Weight Contribution
structure_score 40.0 0.15 6.00
security_score 21.2 0.25 5.30
testing_score 100.0 0.20 20.00
documentation_score 100.0 0.15 15.00
practices_score 89.0 0.15 13.35
code_quality 41.9 0.10 4.19
Overall 1.00 63.8
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all
Severity: Critical 102 High 191 Medium 69 Low 144 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Legacy 291 9-layer 364 Crowd 0 Layer: Security 122 Quality 385 Software 104 Cicd 29 Api 1 Network 12 Hardware 1 Frontend 1

Top 10 actions, ranked by impact × ease. Severity drives impact; tag-based fix-clarity drives ease.

#1
Possible secret in plugins/lookup/passwordstore.py
GapSeverity.CRITICAL Layer.SECURITY score 1.000
Why: critical severity · a leaked credential is a worst-case bug · fix is short / mechanical
Fix: Rotate the credential and remove it from in plugins/lookup/passwordstore.py:184; move to env var / secrets manager.
plugins/lookup/passwordstore.py:184
#2
Possible secret in plugins/lookup/passwordstore.py
GapSeverity.CRITICAL Layer.SECURITY score 1.000
Why: critical severity · a leaked credential is a worst-case bug · fix is short / mechanical
Fix: Rotate the credential and remove it from in plugins/lookup/passwordstore.py:190; move to env var / secrets manager.
plugins/lookup/passwordstore.py:190
#3
Possible secret in plugins/lookup/onepassword_raw.py
GapSeverity.CRITICAL Layer.SECURITY score 1.000
Why: critical severity · a leaked credential is a worst-case bug · fix is short / mechanical
Fix: Rotate the credential and remove it from in plugins/lookup/onepassword_raw.py:43; move to env var / secrets manager.
plugins/lookup/onepassword_raw.py:43
#4
Possible secret in plugins/lookup/keyring.py
GapSeverity.CRITICAL Layer.SECURITY score 1.000
Why: critical severity · a leaked credential is a worst-case bug · fix is short / mechanical
Fix: Rotate the credential and remove it from in plugins/lookup/keyring.py:35; move to env var / secrets manager.
plugins/lookup/keyring.py:35
#5
Possible secret in plugins/lookup/tss.py
GapSeverity.CRITICAL Layer.SECURITY score 1.000
Why: critical severity · a leaked credential is a worst-case bug · fix is short / mechanical
Fix: Rotate the credential and remove it from in plugins/lookup/tss.py:139; move to env var / secrets manager.
plugins/lookup/tss.py:139
#6
Possible secret in plugins/lookup/tss.py
GapSeverity.CRITICAL Layer.SECURITY score 1.000
Why: critical severity · a leaked credential is a worst-case bug · fix is short / mechanical
Fix: Rotate the credential and remove it from in plugins/lookup/tss.py:161; move to env var / secrets manager.
plugins/lookup/tss.py:161
#7
Possible secret in plugins/lookup/tss.py
GapSeverity.CRITICAL Layer.SECURITY score 1.000
Why: critical severity · a leaked credential is a worst-case bug · fix is short / mechanical
Fix: Rotate the credential and remove it from in plugins/lookup/tss.py:249; move to env var / secrets manager.
plugins/lookup/tss.py:249
#8
Possible secret in plugins/lookup/tss.py
GapSeverity.CRITICAL Layer.SECURITY score 1.000
Why: critical severity · a leaked credential is a worst-case bug · fix is short / mechanical
Fix: Rotate the credential and remove it from in plugins/lookup/tss.py:272; move to env var / secrets manager.
plugins/lookup/tss.py:272
#9
Possible secret in plugins/modules/manageiq_group.py
GapSeverity.CRITICAL Layer.SECURITY score 1.000
Why: critical severity · a leaked credential is a worst-case bug · fix is short / mechanical
Fix: Rotate the credential and remove it from in plugins/modules/manageiq_group.py:97; move to env var / secrets manager.
plugins/modules/manageiq_group.py:97
#10
Possible secret in plugins/modules/manageiq_group.py
GapSeverity.CRITICAL Layer.SECURITY score 1.000
Why: critical severity · a leaked credential is a worst-case bug · fix is short / mechanical
Fix: Rotate the credential and remove it from in plugins/modules/manageiq_group.py:108; move to env var / secrets manager.
plugins/modules/manageiq_group.py:108

Click "Find this gap" on any action above to jump to it on the Findings tab. Adjust the chip bar to filter by impact (severity), layer, or source.

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/29433b5c-fbf4-4b2b-a41c-fe10525cb172/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/29433b5c-fbf4-4b2b-a41c-fe10525cb172/

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.