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.

claude-code-templates

https://github.com/davila7/claude-code-templates.git · scanned 2026-05-17 03:09 UTC (13 hours, 11 minutes ago) · 10 languages

903 findings (15 legacy + 888 scanner) 8/10 scanners ran 68th percentile · Python · small (2-20K LoC) Scanner says 50 (higher by 28)

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 13 hours, 11 minutes ago · v2 · 459 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
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all

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

#1
Possible secret in cli-tool/components/skills/scientific/cosmic-database/scripts/download_cosmic.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 cli-tool/components/skills/scientific/cosmic-database/scripts/download_cosmic.py:14; move to env var / secrets manager.
cli-tool/components/skills/scientific/cosmic-database/scripts/download_cosmic.py:14
#2
Possible secret in cli-tool/components/skills/scientific/cosmic-database/scripts/download_cosmic.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 cli-tool/components/skills/scientific/cosmic-database/scripts/download_cosmic.py:203; move to env var / secrets manager.
cli-tool/components/skills/scientific/cosmic-database/scripts/download_cosmic.py:203
#3
Possible secret in cli-tool/components/skills/scientific/labarchive-integration/scripts/setup_config.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 cli-tool/components/skills/scientific/labarchive-integration/scripts/setup_config.py:52; move to env var / secrets manager.
cli-tool/components/skills/scientific/labarchive-integration/scripts/setup_config.py:52
#4
Possible secret in cli-tool/components/skills/scientific/labarchive-integration/scripts/setup_config.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 cli-tool/components/skills/scientific/labarchive-integration/scripts/setup_config.py:58; move to env var / secrets manager.
cli-tool/components/skills/scientific/labarchive-integration/scripts/setup_config.py:58
#5
Possible secret in cli-tool/components/skills/scientific/labarchive-integration/scripts/setup_config.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 cli-tool/components/skills/scientific/labarchive-integration/scripts/setup_config.py:60; move to env var / secrets manager.
cli-tool/components/skills/scientific/labarchive-integration/scripts/setup_config.py:60
#6
Possible secret in cli-tool/components/skills/scientific/research-lookup/lookup.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 cli-tool/components/skills/scientific/research-lookup/lookup.py:61; move to env var / secrets manager.
cli-tool/components/skills/scientific/research-lookup/lookup.py:61
#7
Possible secret in cli-tool/components/skills/scientific/research-lookup/research_lookup.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 cli-tool/components/skills/scientific/research-lookup/research_lookup.py:333; move to env var / secrets manager.
cli-tool/components/skills/scientific/research-lookup/research_lookup.py:333
#8
Possible secret in cli-tool/components/skills/scientific/research-lookup/scripts/research_lookup.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 cli-tool/components/skills/scientific/research-lookup/scripts/research_lookup.py:333; move to env var / secrets manager.
cli-tool/components/skills/scientific/research-lookup/scripts/research_lookup.py:333
#9
Possible secret in cli-tool/components/skills/utilities/playwright-skill/lib/helpers.js
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 cli-tool/components/skills/utilities/playwright-skill/lib/helpers.js:208; move to env var / secrets manager.
cli-tool/components/skills/utilities/playwright-skill/lib/helpers.js:208
#10
Insecure pattern 'private_key_in_repo' in cloudflare-workers/pulse/index.js:572
GapSeverity.CRITICAL Layer.SECURITY score 0.550
Why: critical severity · OWASP-class risk
cloudflare-workers/pulse/index.js:572

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.

{# ── 2026-05-17 Round 14: AI-agent bridge footer ────────────────────── Discoverability: the /agents/voting/ guide + MCP manifest exist but aren't linked from anywhere users actually land. Small, opt-in footer. #}
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/a656f031-2648-4f24-9993-6b291c9bf048/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/a656f031-2648-4f24-9993-6b291c9bf048/

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.