Fission-AI/OpenSpec

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.

41 of your 123 findings came from Repobility's proprietary detections. ✓ Repobility tags below mark them.

Scan timing: clone 4.46s · analysis 18.07s · 5.3 MB · GitHub API rate-limit (preflight)

https://github.com/Fission-AI/OpenSpec · scanned 2026-06-05 11:21 UTC (5 days, 13 hours ago) · 10 languages

334 raw signals (118 security + 216 graph) 63rd percentile · Typescript · medium (20-100K LoC) System graph score 59 (higher by 16)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 5 days, 13 hours ago · v2 · 136 actionable findings from 2 signal sources. 90 repeated signals grouped for readability. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON

77.8% cov · 87 findings

Score breakdown â 2026-05-18-v5

Component	Sub-score	Weight	Contribution
`structure_score`	85.0	0.15	12.75
`security_score`	50.0	0.25	12.50
`testing_score`	100.0	0.20	20.00
`documentation_score`	78.0	0.15	11.70
`practices_score`	82.0	0.15	12.30
`code_quality`	54.5	0.10	5.45
Overall		1.00	74.7

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 4 High 10 Medium 15 Low 94 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 49 System graph 87 Crowd 0 Layer: Software 83 Quality 13 Security 5 Cicd 4 Api 1 Frontend 30

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.

Legacy markers 1 finding

What it is: TODO, FIXME, XXX, HACK comments. Often indicate a known-broken path the author meant to fix.

Why it matters: Each marker is an unfinished thought. Production code shouldn't ship with debt that's documented but not tracked.

How AI causes it: AI mirrors the style of the codebase, so existing TODOs propagate into new code.

Fix approach: Convert each into a ticket. Delete the comment when the ticket lands. Use a pre-commit hook to block new TODOs without an issue link.

1 matching finding on this repo

low File has no detected symbols: test/core/legacy-cleanup.test.ts

View all legacy markers findings →

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

5 matching findings on this repo

low File has no detected symbols: eslint.config.js
low File has no detected symbols: test/commands/config.test.ts
low File has no detected symbols: test/core/global-config.test.ts
low File has no detected symbols: test/core/config-schema.test.ts
low Stray `console.log` in TS/JS — src/commands/config.ts:225

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/d086c264-63cb-47c5-a5b4-d20dc58a8c1f/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/d086c264-63cb-47c5-a5b4-d20dc58a8c1f/

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.