mizchi/crater

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.

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

Scan timing: clone 6.2s · analysis 17.28s · 19.0 MB · GitHub API rate-limit (preflight)

https://github.com/mizchi/crater · scanned 2026-06-05 13:28 UTC (1 week, 2 days ago) · 10 languages

585 raw signals (207 security + 378 graph) 54th percentile · Typescript · medium (20-100K LoC) System graph score 58 (higher by 10)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 1 week, 2 days ago · v2 · 228 actionable findings from 2 signal sources. 168 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 · 140 findings

Score breakdown â 2026-05-18-v5

Component	Sub-score	Weight	Contribution
`structure_score`	60.0	0.15	9.00
`security_score`	40.0	0.25	10.00
`testing_score`	100.0	0.20	20.00
`documentation_score`	86.6	0.15	12.99
`practices_score`	74.0	0.15	11.10
`code_quality`	40.9	0.10	4.09
Overall		1.00	67.2

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 4 High 59 Medium 24 Low 123 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 88 System graph 140 Crowd 0 Layer: Software 117 Quality 59 Security 6 Cicd 2 Api 1 Frontend 43

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 3 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.

3 matching findings on this repo

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

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 `nameToLegacy` in scripts/wpt-dom-runner.ts:606

View all legacy markers findings →

Commented-out code 6 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/`.

6 matching findings on this repo

info Commented-code block (10 lines) in tests/auth-flow-via-bidi.test.ts:135
info Commented-code block (5 lines) in js/playground/utels.js:3
info Commented-code block (5 lines) in scripts/crater_bidi_modules.py:403
info Commented-code block (6 lines) in scripts/fixtures/auth-server.ts:109
info Commented-code block (5 lines) in webdriver/bidi_main/start-with-font.ts:52
info Commented-code block (6 lines) in webdriver/playwright/adapter.ts:735

View all commented-out code findings →

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

7 matching findings on this repo

low Possibly dead Python function: pytest_configure scripts/crater_bidi_adapter.py:622
low File has no detected symbols: playwright.config.ts
low File has no detected symbols: vitest.config.ts
low File has no detected symbols: js/playground/vite.config.js
low File has no detected symbols: scripts/flaker-config-parser.test.ts
low File has no detected symbols: scripts/flaker-config-parser.ts
low File has no detected symbols: scripts/flaker-config-report.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/5464bee6-34a6-4fb3-85e2-7cd7e392ef87/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/5464bee6-34a6-4fb3-85e2-7cd7e392ef87/

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.