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.
33 of your 122 findings came from Repobility's proprietary detections. ✓ Repobility tags below mark them.

Scan timing: clone 5.56s · analysis 31.72s · 14.2 MB · GitHub API rate-limit (preflight)

earendil-works/pi

https://github.com/earendil-works/pi · scanned 2026-06-05 09:45 UTC (5 days, 17 hours ago) · 10 languages

461 raw signals (111 security + 350 graph) 62nd percentile · Typescript · large (100-500K LoC) System graph score 76 (higher by 2)

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

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

JSON
Score breakdown â 2026-05-18-v5
Component Sub-score Weight Contribution
structure_score 60.0 0.15 9.00
security_score 80.0 0.25 20.00
testing_score 95.0 0.20 19.00
documentation_score 77.6 0.15 11.64
practices_score 91.0 0.15 13.65
code_quality 45.7 0.10 4.57
Overall 1.00 77.9
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all

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 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 (5 lines) in packages/ai/test/tokens.test.ts:240
  • info Commented-code block (7 lines) in packages/ai/test/image-tool-result.test.ts:321
  • info Commented-code block (5 lines) in packages/ai/test/context-overflow.test.ts:351
  • info Commented-code block (7 lines) in packages/ai/test/openai-responses-reasoning-r…
  • info Commented-code block (6 lines) in packages/ai/test/anthropic-tool-name-normaliz…
  • info Commented-code block (6 lines) in packages/ai/scripts/generate-models.ts:987
  • info Commented-code block (7 lines) in packages/ai/src/env-api-keys.ts:187
  • info Commented-code block (5 lines) in packages/ai/src/providers/openai-completions.…
  • info Commented-code block (5 lines) in packages/ai/src/providers/transform-messages.…
  • info Commented-code block (6 lines) in packages/tui/test/editor.test.ts:3770
  • info Commented-code block (9 lines) in packages/tui/src/stdin-buffer.ts:208
  • info Commented-code block (7 lines) in packages/tui/src/keys.ts:588
View all commented-out code 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: packages/ai/vitest.config.ts
  • low File has no detected symbols: packages/tui/vitest.config.ts
  • low File has no detected symbols: packages/agent/vitest.harness.config.ts
  • low File has no detected symbols: packages/agent/vitest.config.ts
  • low File has no detected symbols: packages/coding-agent/vitest.config.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/6e92d278-8528-4308-bc39-5eac0ee1c20e/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/6e92d278-8528-4308-bc39-5eac0ee1c20e/

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.