proliferate-ai/proliferate

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.

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

Scan timing: clone 9.25s · analysis 39.61s · 28.9 MB · GitHub API rate-limit (preflight)

https://github.com/proliferate-ai/proliferate · scanned 2026-06-05 22:37 UTC (4 days, 7 hours ago) · 10 languages

1034 raw signals (236 security + 798 graph) 11/13 scanners ran 34th percentile · Typescript · huge (>500K LoC) System graph score 67 (higher by 14)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 4 days, 7 hours ago · v2 · 404 actionable findings from 2 signal sources. 230 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 · 323 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`	83.0	0.20	16.60
`documentation_score`	87.0	0.15	13.05
`practices_score`	79.0	0.15	11.85
`code_quality`	55.0	0.10	5.50
Overall		1.00	81.0

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 4 High 29 Medium 28 Low 158 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 81 System graph 323 Crowd 0 Layer: Quality 109 Security 24 Cicd 10 Software 70 Frontend 138 Hardware 3 Api 50

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

4 matching findings on this repo

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

View all duplicates & near-duplicates findings →

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

5 matching findings on this repo

high [MINED106] Phantom test coverage: test_verify_e2b_webhook_signature_accepts_leg… server/tests/unit/test_e2b_webhooks_integration.py:25
low Old/deprecated-named symbol `price_legacy` in server/tests/integration/test_str…
low Old/deprecated-named symbol `price_legacy` in server/tests/unit/test_billing_do…
low Old/deprecated-named symbol `price_legacy` in server/tests/unit/test_billing_se…
low Old/deprecated-named symbol `relaunch_runtime_nohup_legacy` in server/prolifera…

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 (5 lines) in apps/desktop/src/components/workspace/shell/s…
info Commented-code block (8 lines) in apps/desktop/src/lib/domain/settings/navigati…
info Commented-code block (10 lines) in apps/desktop/src/lib/domain/telemetry/latenc…
info Commented-code block (6 lines) in server/proliferate/auth/desktop/service.py:121
info Commented-code block (5 lines) in server/proliferate/server/cloud/events/servic…
info Commented-code block (6 lines) in server/alembic/versions/a1b2c3d4e5f6_cloud_wo…

View all commented-out code findings →

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

12 matching findings on this repo

high [MINED106] Phantom test coverage: test_send_customerio_welcome_email_asserts_wh… server/tests/unit/test_customerio.py:180
low File has no detected symbols: anyharness/tests/vitest.config.ts
low File has no detected symbols: anyharness/sdk/vitest.config.ts
low File has no detected symbols: anyharness/sdk/src/types/runtime-config.ts
low File has no detected symbols: apps/desktop/tailwind.config.ts
low File has no detected symbols: apps/desktop/vitest.config.ts
info `truncate` class without `title=` for hover reveal — apps/desktop/src/component…
info `truncate` class without `title=` for hover reveal — apps/desktop/src/component…
info `truncate` class without `title=` for hover reveal — apps/packages/product-ui/s…
low Old/deprecated-named symbol `model_copy` in server/proliferate/server/cloud/tar…
low Old/deprecated-named symbol `model_copy` in server/proliferate/server/cloud/run…
low Unused endpoint: GET /{target_id}/configs

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/041dff61-f1a8-477f-bf3d-d64c8c2b6161/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/041dff61-f1a8-477f-bf3d-d64c8c2b6161/

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.