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.

colbymchenry/codegraph

https://github.com/colbymchenry/codegraph.git · scanned 2026-05-16 19:36 UTC (23 hours, 49 minutes ago) · 10 languages

132 findings (22 legacy + 110 scanner) 76th percentile · Typescript · medium (20-100K LoC) Scanner says 76 (higher by 5)

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 23 hours, 49 minutes ago · v2 · 77 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: severity: medium × excluding tests × Reset all
Severity: Critical 0 High 3 Medium 6 Low 54 Source: Legacy 22 9-layer 55 Crowd 0 Layer: Quality 39 Software 21 Frontend 12 Security 2 Cicd 1 Api 2
Corpus Intelligence Cross-corpus context (cohort percentile, top patterns, fix plan) is shown only on repositories you own. Sign up and connect your repo to view it.
Scan summary Repository scanned at 76.1/100 with 88.9% coverage. It contains 709 nodes across 2 cross-layer flows, written primarily in mixed languages. Engine surfaced 55 findings — concentrated in software (20), quality (18), frontend (12). Risk profile is high: 0 critical, 2 high, 4 medium. Recommended next step: open the software layer findings first — that's where the highest-impact wins live.

Showing 6 of 77 findings. Click TP / FP to vote on a finding's accuracy — votes adjust the confidence weighting and improve detection across the platform.

medium Legacy quality error_handling conf 1.00 [ERR002] Empty Catch Block: Empty catch blocks hide errors.
Log the error or rethrow it. Use console.error() at minimum.
src/extraction/index.ts:661 error_handlinglegacy
medium Legacy quality practices No CI/CD configuration found
Add a CI/CD pipeline: create .github/workflows/ci.yml for GitHub Actions with steps to lint, test, and build on every push and pull request.
practiceslegacy
medium 9-layer quality integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — __tests__/extraction.test.ts:300
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
integrityfragile-runtimerobustness
medium 9-layer quality integrity conf 1.00 Frontend route `/users` has no Link/navigate to it — __tests__/frameworks.test.ts
The route is registered but no `<Link to=…>` or `navigate(…)` in the codebase navigates here. Either it's reachable only via direct URL (intentional), it's dead, or the link broke during a refactor.
integrityorphan-pagewiring
medium 9-layer security coverage conf 1.00 No auth library detected
The scanner did not find any standard auth library (JWT, OAuth, NextAuth, Auth0, etc.). Either auth lives in custom code, in a separate service, or is missing.
coverageauth
medium 9-layer cicd coverage conf 1.00 No CI/CD pipelines detected
No GitHub Actions, GitLab CI, or CircleCI configs found. Without CI you can't gate deploys on tests/lints.
coverage
{# ── 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/ed2a4dec-9203-454c-8335-a1c2d105bf62/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/ed2a4dec-9203-454c-8335-a1c2d105bf62/

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.