nicobailon/pi-subagents

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 3.86s · analysis 6.76s · 3.4 MB · GitHub preflight 670ms

https://github.com/nicobailon/pi-subagents.git · scanned 2026-06-01 04:21 UTC (4 days, 9 hours ago) · 10 languages

102 findings (34 legacy + 68 scanner) 68th percentile · Typescript · medium (20-100K LoC) Scanner says 94 (lower by 14)

File as issue Image v2 schema

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 4 days, 9 hours ago · v2 · 68 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

Score breakdown â 2026-05-18-v5

Component	Sub-score	Weight	Contribution
`structure_score`	100.0	0.15	15.00
`security_score`	85.0	0.25	21.25
`testing_score`	90.0	0.20	18.00
`documentation_score`	52.0	0.15	7.80
`practices_score`	72.0	0.15	10.80
`code_quality`	67.4	0.10	6.74
Overall		1.00	79.6

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 0 High 12 Medium 5 Low 43 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Legacy 34 9-layer 34 Crowd 0 Layer: Software 41 Quality 21 Security 3 Api 1 Frontend 1 Cicd 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.

Fragile runtime 14 findings

What it is: Code that runs but breaks under predictable input — division by zero, missing keys, unbounded loops, off-by-one slicing.

Why it matters: Reaches production undetected because happy-path tests pass. First user with a weird input crashes the request.

How AI causes it: AI loves writing the happy path; doesn't probe edge cases unless explicitly asked.

Fix approach: Add property-based tests. Wrap external inputs with explicit validators. Use the framework's typed deserializer (Pydantic, attrs).

12 matching findings on this repo

low Duplicated implementation block across source files src/slash/slash-bridge.ts:142
low Duplicated implementation block across source files src/runs/shared/nested-events.ts:726
low Duplicated implementation block across source files src/intercom/intercom-bridge.ts:120
low Duplicated implementation block across source files src/extension/index.ts:188
info [MINED045] Ts Non Null Assertion: x! asserts not null - bypasses null checks - … src/runs/background/top-level-async.ts:11
info [MINED045] Ts Non Null Assertion: x! asserts not null - bypasses null checks - … src/runs/background/result-watcher.ts:193
info [MINED045] Ts Non Null Assertion: x! asserts not null - bypasses null checks - … src/agents/chain-serializer.ts:97
info [MINED044] Js Console Log Prod: console.log left in code. Should be replaced wi… src/extension/fanout-child.ts:109
info [MINED044] Js Console Log Prod: console.log left in code. Should be replaced wi… src/extension/config.ts:13
info [MINED044] Js Console Log Prod: console.log left in code. Should be replaced wi… install.mjs:24
high [MINED027] React State Array Mutation: state.X.push/splice/sort followed by set… src/runs/shared/long-running-guard.ts:162
high [SEC128] Async function without await — fire-and-forget Promise (AI mistake): A… src/shared/file-coalescer.ts:27

View all fragile runtime findings →

Legacy markers 2 findings

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.

2 matching findings on this repo

low Legacy-named symbol `agents_backup` in test/unit/path-resolution.test.ts:14
low Legacy-named symbol `userDirOld` in src/agents/agents.ts:772

View all legacy markers 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/5767aa70-e926-4344-8830-617ecf01445e/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/5767aa70-e926-4344-8830-617ecf01445e/

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.