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.

Arno125456/pbn-paperclip

https://github.com/Arno125456/pbn-paperclip · scanned 2026-06-17 01:22 UTC (1 month, 2 weeks ago)

771 raw signals (0 security + 771 graph)

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 1 month, 2 weeks ago · v2 · last Δ -27.8 (diff) · 609 actionable findings from 1 signal source. 162 repeated signals grouped for readability. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all

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 `canCreateAgentsLegacy` in server/src/services/auth…
  • low Old/deprecated-named symbol `shouldClearLegacy` in ui/src/pages/AgentDetail.tsx…
  • low Old/deprecated-named symbol `stripe_legacy` in ui/storybook/fixtures/paperclipD…
View all legacy markers findings →
Commented-out code 59 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 (7 lines) in packages/plugins/sandbox-providers/e2b/src/pl…
  • info Commented-code block (6 lines) in packages/plugins/sandbox-providers/exe-dev/sr…
  • info Commented-code block (6 lines) in packages/plugins/sandbox-providers/cloudflare…
  • info Commented-code block (5 lines) in packages/plugins/sandbox-providers/cloudflare…
  • info Commented-code block (8 lines) in packages/plugins/sandbox-providers/cloudflare…
  • info Commented-code block (6 lines) in packages/plugins/sandbox-providers/cloudflare…
  • info Commented-code block (5 lines) in packages/plugins/sandbox-providers/cloudflare…
  • info Commented-code block (5 lines) in packages/plugins/sandbox-providers/daytona/sr…
  • info Commented-code block (7 lines) in packages/plugins/sandbox-providers/modal/src/…
  • info Commented-code block (5 lines) in packages/plugins/plugin-llm-wiki/tests/screen…
  • info Commented-code block (6 lines) in packages/plugins/plugin-llm-wiki/src/ui/app.t…
  • info Commented-code block (7 lines) in packages/adapters/cursor-local/src/index.ts:6
View all commented-out code findings →
Config drift 26 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
  • 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…
  • medium Insecure pattern 'node_child_process' in server/src/config.ts:2 server/src/config.ts:2
  • critical Possible secret in server/src/__tests__/environment-config.test.ts server/src/__tests__/environment-config.test.ts:150
  • medium Insecure pattern 'node_child_process' in cli/src/config/server-bind.ts:1 cli/src/config/server-bind.ts:1
  • low Very large file: ui/src/components/AgentConfigForm.tsx (1844 lines)
  • high Agent instruction/config may expose a secret: packages/skills-catalog/catalog/b… packages/skills-catalog/catalog/bundled/software-…:4
  • high Agent instruction/config may expose a secret: packages/skills-catalog/catalog/b… packages/skills-catalog/catalog/bundled/paperclip…:4
  • high Agent instruction/config may expose a secret: packages/skills-catalog/catalog/b… packages/skills-catalog/catalog/bundled/paperclip…:4
  • high Agent instruction/config may expose a secret: packages/skills-catalog/catalog/b… packages/skills-catalog/catalog/bundled/docs/doc-…:4
  • high Agent instruction/config may expose a secret: packages/skills-catalog/catalog/b… packages/skills-catalog/catalog/bundled/quality/q…:4
  • high Agent instruction/config may expose a secret: packages/skills-catalog/catalog/b… packages/skills-catalog/catalog/bundled/product/w…:4
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/aaf4bce5-a7bc-401d-97f8-ced72d2cb18d/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/aaf4bce5-a7bc-401d-97f8-ced72d2cb18d/

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.