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.
78 of your 182 findings came from Repobility's proprietary detections. ✓ Repobility tags below mark them.

Scan timing: clone 16.11s · analysis 14.2s · 38.7 MB · GitHub API rate-limit (preflight)

screenpipe/screenpipe

https://github.com/screenpipe/screenpipe · scanned 2026-06-05 17:44 UTC (4 days, 21 hours ago) · 10 languages

1385 raw signals (161 security + 1224 graph) 11/13 scanners ran 95th percentile · Rust · large (100-500K LoC) System graph score 44 (higher by 41)

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

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

JSON
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 86.0 0.20 17.20
documentation_score 84.0 0.15 12.60
practices_score 96.0 0.15 14.40
code_quality 70.0 0.10 7.00
Overall 1.00 85.2
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

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 2 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.
2 matching findings on this repo
  • low Old/deprecated-named symbol `manualLegacy` in apps/screenpipe-app-tauri/lib/uti…
  • low Old/deprecated-named symbol `validateAuthLegacy` in packages/ai-gateway/src/uti…
View all legacy markers findings →
Commented-out code 93 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 (6 lines) in apps/screenpipe-app-tauri/vitest.config.ts:12
  • info Commented-code block (5 lines) in apps/screenpipe-app-tauri/scripts/pre_build.j…
  • info Commented-code block (6 lines) in apps/screenpipe-app-tauri/components/browser-…
  • info Commented-code block (5 lines) in apps/screenpipe-app-tauri/components/update-b…
  • info Commented-code block (8 lines) in apps/screenpipe-app-tauri/components/theme-pr…
  • info Commented-code block (5 lines) in apps/screenpipe-app-tauri/components/chat-sid…
  • info Commented-code block (5 lines) in apps/screenpipe-app-tauri/components/notifica…
  • info Commented-code block (6 lines) in apps/screenpipe-app-tauri/components/standalo…
  • info Commented-code block (5 lines) in apps/screenpipe-app-tauri/components/settings…
  • info Commented-code block (5 lines) in apps/screenpipe-app-tauri/components/settings…
  • info Commented-code block (7 lines) in apps/screenpipe-app-tauri/components/settings…
  • info Commented-code block (6 lines) in apps/screenpipe-app-tauri/components/settings…
View all commented-out code findings →
Config drift 5 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.
5 matching findings on this repo
  • high [AUC003] Object-level route lacks visible authorization: A route with an object… crates/screenpipe-engine/src/connections_api.rs:2539
  • low File has no detected symbols: apps/screenpipe-app-tauri/tailwind.config.ts
  • low File has no detected symbols: apps/screenpipe-app-tauri/vitest.config.ts
  • info Commented-code block (6 lines) in apps/screenpipe-app-tauri/vitest.config.ts:12
  • info Commented-code block (8 lines) in ee/sdk/examples/tauri-app/vite.config.js:7
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/1bdba35f-ca3c-4a95-82bb-1ef852d02a25/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/1bdba35f-ca3c-4a95-82bb-1ef852d02a25/

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.