open-gsd/gsd-pi

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.

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

Scan timing: clone 18.86s · analysis 28.56s · 43.9 MB · GitHub API rate-limit (preflight)

https://github.com/open-gsd/gsd-pi · scanned 2026-06-05 17:49 UTC (4 days, 21 hours ago) · 10 languages

1559 raw signals (209 security + 1350 graph) 11/13 scanners ran 95th percentile · Typescript · huge (>500K LoC) System graph score 59 (higher by 33)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

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

JSON

100.0% cov · 624 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`	86.0	0.15	12.90
`code_quality`	67.0	0.10	6.70
Overall		1.00	92.4

security_score may be inflated — optional security scanners were skipped on this fast scan

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 0 High 38 Medium 27 Low 280 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 74 System graph 624 Crowd 0 Layer: Software 60 Quality 432 Security 29 Cicd 10 Api 1 Frontend 161 Hardware 5

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 1 finding

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.

1 matching finding on this repo

low Near-duplicate function bodies in 2 places

View all duplicates & near-duplicates findings →

Legacy markers 4 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.

4 matching findings on this repo

low Old/deprecated-named symbol `sliceLockLegacy` in src/resources/extensions/gsd/s…
info Commented-code block (5 lines) in src/resources/extensions/gsd/parsers-legacy.t…
low Old/deprecated-named symbol `nLegacy` in src/resources/extensions/gsd/tests/sta…
low Old/deprecated-named symbol `fromLegacy` in src/resources/extensions/gsd/tests/…

View all legacy markers findings →

Commented-out code 297 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 tests/live-regression/run.ts:204
info Commented-code block (5 lines) in tests/e2e/agent-loop.e2e.test.ts:78
info Commented-code block (5 lines) in tests/e2e/agent-loop-multiturn.e2e.test.ts:128
info Commented-code block (8 lines) in scripts/validate-pack.js:144
info Commented-code block (5 lines) in packages/pi-ai/test/tokens.test.ts:234
info Commented-code block (7 lines) in packages/pi-ai/test/image-tool-result.test.ts…
info Commented-code block (5 lines) in packages/pi-ai/test/context-overflow.test.ts:…
info Commented-code block (7 lines) in packages/pi-ai/test/openai-responses-reasonin…
info Commented-code block (6 lines) in packages/pi-ai/test/anthropic-tool-name-norma…
info Commented-code block (6 lines) in packages/pi-ai/scripts/generate-models.ts:880
info Commented-code block (7 lines) in packages/pi-ai/src/env-api-keys.ts:215
info Commented-code block (5 lines) in packages/pi-ai/src/utils/repair-tool-json.ts:…

View all commented-out code findings →

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

2 matching findings on this repo

low File has no detected symbols: packages/pi-ai/vitest.config.ts
low File has no detected symbols: packages/pi-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/a8bbe502-1101-4083-8daf-950504877fed/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/a8bbe502-1101-4083-8daf-950504877fed/

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.