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 (1 week ago) · 10 languages

552 findings (111 legacy + 441 scanner) 35th percentile · Typescript · large (100-500K LoC) Scanner says 49 (higher by 23)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 1 week ago · v1 · 552 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

100.0% cov · 441 gaps

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 261 Medium 37 Low 135 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Legacy 111 9-layer 441 Crowd 0 Layer: Security 8 Quality 135 Software 91 Cicd 44 Frontend 68 Hardware 5 Api 201

Exclude dismissed / FP Exclude test files

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

Possible secret in packages/paths/src/telemetry.ts

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 packages/paths/src/telemetry.ts:46; move to env var / secrets manager.

packages/paths/src/telemetry.ts:46

Dangling fetch: POST https://slack.com/api/auth.test (packages/cli/src/commands/doctor.ts:214)

GapSeverity.HIGH Layer.API score 0.338

Why: high severity · contract mismatch FE↔BE

Fix: Confirm the FE call URL matches a backend endpoint; update one side.

Dangling fetch: GET https://api.telegram.org/bot${token}/getMe (packages/cli/src/commands/doctor.ts:241)

GapSeverity.HIGH Layer.API score 0.338

Why: high severity · contract mismatch FE↔BE

Fix: Confirm the FE call URL matches a backend endpoint; update one side.

Dangling fetch: GET /api/artifacts/${encodeURIComponent(runId)}/${encodedFilename} (packages/web/src/components/workflows/ArtifactViewerModal.tsx:92)

GapSeverity.HIGH Layer.API score 0.338

Why: high severity · contract mismatch FE↔BE

Fix: Confirm the FE call URL matches a backend endpoint; update one side.

Dangling fetch: GET /api/artifacts/${encodeURIComponent(runId)}/${encodedPath} (packages/web/src/experiments/console/skills/runs.ts:129)

GapSeverity.HIGH Layer.API score 0.338

Why: high severity · contract mismatch FE↔BE

Fix: Confirm the FE call URL matches a backend endpoint; update one side.

Insecure pattern 'cors_wildcard' in packages/server/src/routes/api.ts:914

GapSeverity.MEDIUM Layer.SECURITY score 0.248

Why: medium severity · OWASP-class risk

packages/server/src/routes/api.ts:914

GitHub Action is tag-pinned rather than SHA-pinned

GapSeverity.MEDIUM Layer.CICD score 0.225

Why: medium severity

.github/workflows/test.yml:23

GitHub Action is tag-pinned rather than SHA-pinned

GapSeverity.MEDIUM Layer.CICD score 0.225

Why: medium severity

.github/workflows/test.yml:54

GitHub Action is tag-pinned rather than SHA-pinned

GapSeverity.MEDIUM Layer.CICD score 0.225

Why: medium severity

.github/workflows/test.yml:57

#10

GitHub Action is tag-pinned rather than SHA-pinned

GapSeverity.MEDIUM Layer.CICD score 0.225

Why: medium severity

.github/workflows/e2e-smoke.yml:20

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.

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.