github/spec-kit

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.

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

Scan timing: clone 3.01s · analysis 4.96s · 4.2 MB · GitHub API rate-limit (preflight)

https://github.com/github/spec-kit · scanned 2026-06-11 23:26 UTC (1 day, 10 hours ago) · 10 languages

735 raw signals (72 security + 663 graph) 99th percentile · Python · medium (20-100K LoC)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 1 day, 10 hours ago · v8 · 92 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

88.9% cov · 62 findings

Score breakdown â 2026-05-18-v5

Component	Sub-score	Weight	Contribution
`structure_score`	85.0	0.15	12.75
`security_score`	100.0	0.25	25.00
`testing_score`	100.0	0.20	20.00
`documentation_score`	100.0	0.15	15.00
`practices_score`	89.0	0.15	13.35
`code_quality`	38.3	0.10	3.83
Overall		1.00	89.9

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 0 High 3 Medium 3 Low 41 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 30 System graph 62 Crowd 0 Layer: Quality 73 Security 2 Cicd 3 Software 12 Api 1 Frontend 1

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.

Duplicates & near-duplicates 6 findings

What it is: Same function copy-pasted into multiple modules with minor variations.

Why it matters: Each copy drifts independently — bug fixes apply to one, miss the others.

How AI causes it: AI completes the same pattern in each file rather than refactoring to a shared helper.

Fix approach: Extract the duplicated logic into the most general module both call sites already import. Add tests at the helper level.

6 matching findings on this repo

low Near-duplicate function bodies in 2 places repo-level
low Near-duplicate function bodies in 4 places
low Near-duplicate function bodies in 12 places
low Near-duplicate function bodies in 3 places repo-level
low Near-duplicate function bodies in 15 places
low Near-duplicate function bodies in 8 places

View all duplicates & near-duplicates findings →

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 Old/deprecated-named symbol `test_canonical_dir_preferred_over_legacy` in tests…

View all legacy markers findings →

Commented-out code 23 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 (8 lines) in tests/test_self_upgrade_verification.py:629
info Commented-code block (5 lines) in tests/test_workflows.py:2572
info Commented-code block (6 lines) in tests/self_upgrade_helpers.py:40
info Commented-code block (5 lines) in tests/integrations/test_manifest.py:77
info Commented-code block (7 lines) in tests/integrations/test_integration_subcomman…
info Commented-code block (8 lines) in tests/integrations/test_integration_kiro_cli.…
info Commented-code block (6 lines) in src/specify_cli/_version.py:788
info Commented-code block (10 lines) in src/specify_cli/__init__.py:2
info Commented-code block (7 lines) in src/specify_cli/_utils.py:48
info Commented-code block (6 lines) in src/specify_cli/integration_state.py:38
info Commented-code block (7 lines) in src/specify_cli/shared_infra.py:402
info Commented-code block (6 lines) in src/specify_cli/agents.py:31

View all commented-out code 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/fd7adca4-f4b6-4783-9a75-00a79d91bfd4/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/fd7adca4-f4b6-4783-9a75-00a79d91bfd4/

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.