paperclipai/paperclip

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.

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)

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

100.0% cov · 449 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`	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

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.

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

3 matching findings on this repo

low Old/deprecated-named symbol `stripe_legacy` in ui/storybook/fixtures/paperclipD…
low Old/deprecated-named symbol `shouldClearLegacy` in ui/src/pages/AgentDetail.tsx…
low Old/deprecated-named symbol `canCreateAgentsLegacy` in server/src/services/auth…

View all legacy markers findings →

Commented-out code 49 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 (8 lines) in ui/storybook/stories/sub-issues-workflow.stor…
info Commented-code block (6 lines) in ui/src/components/NewIssueDialog.tsx:1224
info Commented-code block (5 lines) in ui/src/components/IssueChatThread.test.tsx:673
info Commented-code block (6 lines) in ui/src/components/IssueChatThread.tsx:2801
info Commented-code block (5 lines) in ui/src/lib/issue-reference.ts:51
info Commented-code block (14 lines) in packages/adapters/opencode-local/src/index.t…
info Commented-code block (5 lines) in packages/adapters/opencode-local/src/server/t…
info Commented-code block (5 lines) in packages/adapters/opencode-local/src/server/r…
info Commented-code block (7 lines) in packages/adapters/cursor-local/src/index.ts:6
info Commented-code block (7 lines) in packages/adapters/acpx-local/src/server/execu…
info Commented-code block (5 lines) in packages/adapters/gemini-local/src/server/par…
info Commented-code block (6 lines) in packages/adapters/pi-local/src/server/execute…

View all commented-out code findings →

Config drift 13 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 [MINED113] Express POST /companies/:companyId/environments/probe-config has no … server/src/routes/environments.ts:428
low File has no detected symbols: vitest.config.ts
low File has no detected symbols: tests/release-smoke/playwright.config.ts
low File has no detected symbols: tests/e2e/playwright.config.ts
low File has no detected symbols: tests/e2e/playwright-multiuser.config.ts
low File has no detected symbols: tests/e2e/playwright-multiuser-authenticated.conf…
low File has no detected symbols: ui/vite.config.ts
low File has no detected symbols: ui/vitest.config.ts
info `truncate` class without `title=` for hover reveal — ui/src/adapters/schema-con…
info `truncate` class without `title=` for hover reveal — ui/src/components/AgentCon…
low Very large file: ui/src/components/AgentConfigForm.tsx (1844 lines)
info Commented-code block (5 lines) in packages/adapters/opencode-local/src/server/r…

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