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.

davila7/claude-code-templates

https://github.com/davila7/claude-code-templates · scanned 2026-06-17 01:59 UTC (1 month, 1 week ago)

986 raw signals (0 security + 986 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 1 month, 1 week ago · v2 · last Δ -35.3 (diff) · 928 actionable findings from 1 signal source. 58 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 · 928 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 13 High 177 Medium 514 Low 185 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 928 Crowd 0 Layer: Software 14 Frontend 96 Network 13 Hardware 1 Security 342 Cicd 3 Quality 382 Api 77

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 3 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.

3 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 4 places

View all duplicates & near-duplicates findings →

Commented-out code 18 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 (5 lines) in cli-tool/components/skills/productivity/skill…
info Commented-code block (5 lines) in cli-tool/components/skills/development/skill-…
info Commented-code block (8 lines) in cli-tool/components/skills/development/system…
info Commented-code block (5 lines) in cli-tool/components/skills/development/skill-…
info Commented-code block (5 lines) in cli-tool/components/skills/scientific/stable-…
info Commented-code block (6 lines) in cli-tool/components/skills/scientific/stable-…
info Commented-code block (8 lines) in cli-tool/components/skills/scientific/stable-…
info Commented-code block (8 lines) in cli-tool/components/skills/scientific/pydicom…
info Commented-code block (5 lines) in cli-tool/components/skills/scientific/matplot…
info Commented-code block (5 lines) in cli-tool/components/skills/scientific/documen…
info Commented-code block (6 lines) in cli-tool/components/skills/scientific/documen…
info Commented-code block (5 lines) in cli-tool/components/skills/scientific/researc…

View all commented-out code findings →

Config drift 108 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.

12 matching findings on this repo

medium Runtime service client appears to use placeholder configuration
high Agent instruction/config may expose a secret: CLAUDE.md CLAUDE.md:367
high Agent instruction/config may expose a secret: cli-tool/components/skills/produc… cli-tool/components/skills/productivity/nowait/SK…:100
high Agent instruction/config may expose a secret: cli-tool/components/skills/produc… cli-tool/components/skills/productivity/notion-sp…:43
high Agent instruction/config may expose a secret: cli-tool/components/skills/develo… cli-tool/components/skills/development/cocoindex/…:113
high Agent instruction/config may expose a secret: cli-tool/components/skills/develo… cli-tool/components/skills/development/prometheus…:168
high Agent instruction/config may expose a secret: cli-tool/components/skills/develo… cli-tool/components/skills/development/k6-load-te…:179
high Agent instruction/config may expose a secret: cli-tool/components/skills/develo… cli-tool/components/skills/development/code-revie…:177
high Agent instruction/config may expose a secret: cli-tool/components/skills/develo… cli-tool/components/skills/development/cc-skill-b…:98
high Agent instruction/config may expose a secret: cli-tool/components/skills/develo… cli-tool/components/skills/development/zapier-wor…:499
high Agent instruction/config may expose a secret: cli-tool/components/skills/develo… cli-tool/components/skills/development/production…:281
high Agent instruction/config may expose a secret: cli-tool/components/skills/develo… cli-tool/components/skills/development/aws-server…:111

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/b8a542d3-f9d7-42c7-8a0b-3d8cfa7f0776/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/b8a542d3-f9d7-42c7-8a0b-3d8cfa7f0776/

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.