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.
Sign up free Scan another repo
91 of your 201 findings came from Repobility's proprietary detections. ✓ Repobility tags below mark them.

Scan timing: clone 18.8s · analysis 19.43s · 53.2 MB · GitHub API rate-limit (preflight)

paperclipai/paperclip

https://github.com/paperclipai/paperclip · scanned 2026-06-05 08:36 UTC (5 days, 20 hours ago) · 10 languages

1360 raw signals (182 security + 1178 graph) 11/13 scanners ran 56th percentile · Typescript · huge (>500K LoC) System graph score 59 (higher by 27)

File as issue Image
UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

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

JSON
Combined
70.5
/100
Security checks
82
83 findings
System graph
59
100.0% cov · 449 findings
Critical
11
click to filter
Agents
6
0 votes
Crowd
0
reported
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 100.0 0.20 20.00
documentation_score 75.0 0.15 11.25
practices_score 91.0 0.15 13.65
code_quality 70.0 0.10 7.00
Overall 1.00 85.9
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 11 High 54 Medium 44 Low 269 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 83 System graph 449 Crowd 0 Layer: Quality 223 Cicd 14 Software 55 Security 17 Frontend 151 Hardware 7 Api 65

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

#1
Possible secret in cli/src/commands/routines.ts
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 cli/src/commands/routines.ts:137; move to env var / secrets manager.
cli/src/commands/routines.ts:137
#2
Possible secret in cli/src/commands/worktree.ts
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 cli/src/commands/worktree.ts:1080; move to env var / secrets manager.
cli/src/commands/worktree.ts:1080
#3
Possible secret in packages/db/src/migration-runtime.ts
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 packages/db/src/migration-runtime.ts:142; move to env var / secrets manager.
packages/db/src/migration-runtime.ts:142
#4
Possible secret in packages/db/src/test-embedded-postgres.ts
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 packages/db/src/test-embedded-postgres.ts:94; move to env var / secrets manager.
packages/db/src/test-embedded-postgres.ts:94
#5
Possible secret in server/src/index.ts
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/src/index.ts:415; move to env var / secrets manager.
server/src/index.ts:415
#6
pull_request_target workflow appears to check out untrusted PR code
GapSeverity.HIGH Layer.CICD score 0.375
Why: high severity
.github/workflows/commitperclip-review.yml
#7
`dangerouslySetInnerHTML` used in a React component — ui/src/components/MarkdownBody.tsx:546
GapSeverity.MEDIUM Layer.FRONTEND score 0.360
Why: medium severity
#8
Dangling fetch: POST /api/auth${path} (ui/src/api/auth.ts:64)
GapSeverity.HIGH Layer.API score 0.338
Why: high severity · contract mismatch FE↔BE
Fix: Confirm the FE call URL matches a backend endpoint; update one side.
#9
Dangling fetch: PATCH /api/auth${path} (ui/src/api/auth.ts:78)
GapSeverity.HIGH Layer.API score 0.338
Why: high severity · contract mismatch FE↔BE
Fix: Confirm the FE call URL matches a backend endpoint; update one side.
#10
Dangling fetch: GET /api/auth/get-session (ui/src/api/auth.ts:93)
GapSeverity.HIGH Layer.API score 0.338
Why: high severity · contract mismatch FE↔BE
Fix: Confirm the FE call URL matches a backend endpoint; update one side.

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/a1e662d5-1d23-4b66-ba05-c8e988b06053/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/a1e662d5-1d23-4b66-ba05-c8e988b06053/

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.