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

Top 10 actions, ranked by impact × ease. Severity drives impact; tag-based fix-clarity drives ease.

Possible secret in server/proliferate/auth/passwords.py

GapSeverity.CRITICAL Layer.SECURITY score 1.000

Why: critical severity · a leaked credential is a worst-case bug · fix is short / mechanical

Fix: Rotate the credential and remove it from in server/proliferate/auth/passwords.py:14; move to env var / secrets manager.

server/proliferate/auth/passwords.py:14

Possible secret in server/scripts/provision_password_auth_user.py

GapSeverity.CRITICAL Layer.SECURITY score 1.000

Why: critical severity · a leaked credential is a worst-case bug · fix is short / mechanical

Fix: Rotate the credential and remove it from in server/scripts/provision_password_auth_user.py:111; move to env var / secrets manager.

server/scripts/provision_password_auth_user.py:111

Possible secret in server/deploy/ensure-secrets.sh

GapSeverity.CRITICAL Layer.SECURITY score 1.000

Why: critical severity · a leaked credential is a worst-case bug · fix is short / mechanical

Fix: Rotate the credential and remove it from in server/deploy/ensure-secrets.sh:177; move to env var / secrets manager.

server/deploy/ensure-secrets.sh:177

FastAPI POST `web_session_logout` without auth dependency — server/proliferate/auth/identity/api.py:398

GapSeverity.HIGH Layer.SECURITY score 0.537

Why: high severity · OWASP-class risk

Fix: Add `user = Depends(get_current_user)` to the function signature in server/proliferate/auth/identity/api.py:398.

server/proliferate/auth/identity/api.py:398

FastAPI POST `worker_control_wait_endpoint` without auth dependency — server/proliferate/server/cloud/worker/api.py:138

GapSeverity.HIGH Layer.SECURITY score 0.537

Why: high severity · OWASP-class risk

Fix: Add `user = Depends(get_current_user)` to the function signature in server/proliferate/server/cloud/worker/api.py:138.

server/proliferate/server/cloud/worker/api.py:138

FastAPI POST `stripe_webhook_endpoint` without auth dependency — server/proliferate/server/billing/api.py:241

GapSeverity.HIGH Layer.SECURITY score 0.537

Why: high severity · OWASP-class risk

Fix: Add `user = Depends(get_current_user)` to the function signature in server/proliferate/server/billing/api.py:241.

server/proliferate/server/billing/api.py:241

Insecure pattern 'eval_used' in server/proliferate/server/artifact_runtime/static/assets/index-CP1RUuvQ.js:244

GapSeverity.HIGH Layer.SECURITY score 0.413

Why: high severity · OWASP-class risk

server/proliferate/server/artifact_runtime/static/assets/index-CP1RUuvQ.js:244

`dangerouslySetInnerHTML` used in a React component — apps/desktop/src/components/workspace/files/file-icons.tsx:47

GapSeverity.MEDIUM Layer.FRONTEND score 0.360

Why: medium severity

`dangerouslySetInnerHTML` used in a React component — apps/desktop/src/components/content/ui/HighlightedCodePanel.tsx:92

GapSeverity.MEDIUM Layer.FRONTEND score 0.360

Why: medium severity

#10

`dangerouslySetInnerHTML` used in a React component — apps/desktop/src/components/content/ui/MarkdownRenderer.tsx:33

GapSeverity.MEDIUM Layer.FRONTEND score 0.360

Why: medium severity

Click "Find this gap" on any action above to jump to it on the Findings tab. Adjust the chip bar to filter by impact (severity), layer, or source.

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.