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.

mattpocock/skills

https://github.com/mattpocock/skills · scanned 2026-07-23 10:41 UTC (5 days, 8 hours ago) · 10 languages

37 raw signals (3 security + 34 graph) 8th percentile · Unknown ·

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 5 days, 8 hours ago · v4 · last Δ +27.1 (diff) · 36 actionable findings from 2 signal sources. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON

60.0% cov · 34 findings

Score breakdown â 2026-05-14-v3

Component	Sub-score	Weight	Contribution
`structure_score`	45.0	0.15	6.75
`security_score`	100.0	0.25	25.00
`testing_score`	0.0	0.20	0.00
`documentation_score`	60.0	0.15	9.00
`practices_score`	30.0	0.15	4.50
`code_quality`	80.0	0.10	8.00
Overall		1.00	53.2

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 0 High 4 Medium 29 Low 0 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 2 System graph 34 Crowd 0 Layer: Quality 24 Security 7 Cicd 2 Dependencies 3

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.

Commented-out code 1 finding

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/`.

1 matching finding on this repo

info Commented-code block (7 lines) in skills/in-progress/setup-ts-deep-modules/depe…

View all commented-out code findings →

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

3 matching findings on this repo

medium No CI/CD configuration found
medium CI is configured but no tests are detected
info Commented-code block (7 lines) in skills/in-progress/setup-ts-deep-modules/depe…

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/e88c5107-1258-492a-8d47-b0a1e1b3ec1e/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/e88c5107-1258-492a-8d47-b0a1e1b3ec1e/

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.