coleam00/Archon

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.

Scan timing: clone 2.74s · analysis 7.06s · 10.1 MB · GitHub API rate-limit (preflight)

https://github.com/coleam00/Archon.git · scanned 2026-05-29 03:46 UTC (2 weeks, 1 day ago) · 10 languages

552 raw signals (111 security + 441 graph) 37th percentile · Typescript · large (100-500K LoC) System graph score 49 (higher by 23)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 2 weeks, 1 day ago · v1 · 457 actionable findings from 2 signal sources. 95 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 · 411 findings

Score breakdown â 2026-05-18-v5

Component	Sub-score	Weight	Contribution
`structure_score`	60.0	0.15	9.00
`security_score`	57.3	0.25	14.32
`testing_score`	85.0	0.20	17.00
`documentation_score`	100.0	0.15	15.00
`practices_score`	77.0	0.15	11.55
`code_quality`	52.2	0.10	5.22
Overall		1.00	72.1

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 2 High 205 Medium 14 Low 121 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 46 System graph 411 Crowd 0 Layer: Security 6 Quality 107 Software 55 Cicd 16 Frontend 68 Hardware 4 Api 201

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 56 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 packages/adapters/src/forge/github/adapter.ts…
info Commented-code block (5 lines) in packages/adapters/src/forge/github/adapter.te…
info Commented-code block (5 lines) in packages/adapters/src/community/forge/gitlab/…
info Commented-code block (5 lines) in packages/cli/src/commands/workflow.ts:520
info Commented-code block (5 lines) in packages/cli/src/commands/setup.ts:1501
info Commented-code block (5 lines) in packages/paths/src/env-loader.test.ts:151
info Commented-code block (7 lines) in packages/git/src/git.test.ts:6
info Commented-code block (5 lines) in packages/git/src/worktree.ts:367
info Commented-code block (6 lines) in packages/providers/src/shared/structured-outp…
info Commented-code block (8 lines) in packages/providers/src/community/pi/provider.…
info Commented-code block (5 lines) in packages/providers/src/community/pi/provider.…
info Commented-code block (8 lines) in packages/providers/src/community/pi/event-bri…

View all commented-out code findings →

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

6 matching findings on this repo

low File has no detected symbols: packages/providers/src/community/pi/config.test.ts
low File has no detected symbols: packages/providers/src/community/copilot/config.t…
info Commented-code block (6 lines) in packages/core/src/config/config-loader.ts:266
high Dangling fetch: GET /api/config (packages/server/src/routes/api.health.test.ts:…
high Dangling fetch: GET /api/config (packages/server/src/routes/api.health.test.ts:…
high Dangling fetch: GET /api/config (packages/server/src/routes/api.health.test.ts:…

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/03f8e180-87b4-4749-b483-9718dabd5226/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/03f8e180-87b4-4749-b483-9718dabd5226/

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.