PerryTS/perry

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.

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

https://github.com/PerryTS/perry · scanned 2026-06-05 19:19 UTC (4 days, 17 hours ago) · 10 languages

10278 raw signals (93 security + 10185 graph) 11/13 scanners ran 51st percentile · Rust · large (100-500K LoC) System graph score 44 (higher by 25)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 4 days, 17 hours ago · v2 · 5042 actionable findings from 2 signal sources. 144 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 · 5011 findings

Score breakdown â 2026-05-18-v5

Component	Sub-score	Weight	Contribution
`structure_score`	60.0	0.15	9.00
`security_score`	100.0	0.25	25.00
`testing_score`	20.0	0.20	4.00
`documentation_score`	76.0	0.15	11.40
`practices_score`	82.0	0.15	12.30
`code_quality`	67.0	0.10	6.70
Overall		1.00	68.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 18 High 33 Medium 38 Low 4091 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 31 System graph 5011 Crowd 0 Layer: Cicd 6 Quality 1057 Software 56 Frontend 3853 Network 8 Hardware 4 Security 37 Api 21

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 repo-level
low Near-duplicate function bodies in 4 places

View all duplicates & near-duplicates findings →

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

12 matching findings on this repo

low Stray `console.log` in TS/JS — test-files/test_decorators_legacy_metadata.ts:22
low Stray `console.log` in TS/JS — test-files/test_decorators_legacy_methods.ts:34
low Stray `console.log` in TS/JS — test-files/test_decorators_legacy_property_metad…
low Stray `console.log` in TS/JS — test-files/test_decorators_legacy_metadata_impor…
low Stray `console.log` in TS/JS — test-files/test_decorators_legacy_module_args.ts…
low Stray `console.log` in TS/JS — test-parity/node-suite/crypto/x509/signature-leg…
low Stray `console.log` in TS/JS — test-parity/node-suite/util/legacy-helpers.ts:9
low Stray `console.log` in TS/JS — test-parity/node-suite/stream/constructor/stream…
low Stray `console.log` in TS/JS — test-parity/node-suite/url/module/legacy-url-exp…
low Stray `console.log` in TS/JS — test-parity/node-suite/url/module/legacy-parse-r…
low Stray `console.log` in TS/JS — test-parity/node-suite/url/legacy/format-options…
low Stray `console.log` in TS/JS — test-parity/node-suite/url/legacy/parse-string-q…

View all legacy markers findings →

Commented-out code 842 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 types/perry/updater/index.d.ts:3
info Commented-code block (5 lines) in types/perry/tui/index.d.ts:3
info Commented-code block (8 lines) in types/perry/ui/index.d.ts:789
info Commented-code block (7 lines) in types/perry/ads/index.d.ts:4
info Commented-code block (10 lines) in types/perry/audio/index.d.ts:6
info Commented-code block (9 lines) in types/perry/system/index.d.ts:305
info Commented-code block (5 lines) in types/perry/pdf/index.d.ts:4
info Commented-code block (38 lines) in types/perry/background/index.d.ts:4
info Commented-code block (5 lines) in types/perry/webassembly/index.d.ts:3
info Commented-code block (6 lines) in tests/wasm/21_class_method_i64.ts:3
info Commented-code block (7 lines) in tests/wasm/20_string_from_char_code.ts:1
info Commented-code block (5 lines) in tests/wasm/23_timers.ts:1

View all commented-out code findings →

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

6 matching findings on this repo

low Stray `console.log` in TS/JS — test-parity/node-suite/process/config/config.ts:8
low Stray `console.log` in TS/JS — test-parity/node-suite/util/parse-args/invalid-c…
low Stray `console.log` in TS/JS — test-parity/node-suite/stream/finished/options-c…
info Commented-code block (6 lines) in test-parity/node-suite/process/config/config.…
high Dangling fetch: GET https://api.example.com/stock/${config.symbol} (docs/exampl…
high Dangling fetch: GET https://app.searchbird.io/api/sites?days=${config.dateRange…

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/3745be9b-7f14-4c23-b30a-b764b629630e/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/3745be9b-7f14-4c23-b30a-b764b629630e/

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.