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.

saross/personal-assistant

https://github.com/saross/personal-assistant · scanned 2026-06-16 00:02 UTC (2 months, 3 weeks ago)

77 raw signals (0 security + 77 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 2 months, 3 weeks ago · v1 · 72 actionable findings from 1 signal source. 5 repeated signals grouped for readability. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON

88.9% cov · 72 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 0 High 0 Medium 10 Low 19 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 72 Crowd 0 Layer: Software 7 Network 1 Frontend 1 Security 1 Cicd 1 Quality 61

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.

Duplicates & near-duplicates 2 findings

What it is: Same function copy-pasted into multiple modules with minor variations.

Why it matters: Each copy drifts independently — bug fixes apply to one, miss the others.

How AI causes it: AI completes the same pattern in each file rather than refactoring to a shared helper.

Fix approach: Extract the duplicated logic into the most general module both call sites already import. Add tests at the helper level.

2 matching findings on this repo

low Near-duplicate function bodies in 3 places repo-level
low Near-duplicate function bodies in 2 places repo-level

View all duplicates & near-duplicates findings →

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 `skipped_legacy` in tests/test_sync_to_zotero.py:365
low Old/deprecated-named symbol `skipped_legacy` in scripts/sync-to-zotero.py:175

View all legacy markers findings →

Commented-out code 41 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 tests/test_extraction_hook.py:224
info Commented-code block (8 lines) in tests/test_rebuild_postgres.py:367
info Commented-code block (6 lines) in tests/test_jsonl_flock.py:263
info Commented-code block (5 lines) in tests/test_sync_script.py:459
info Commented-code block (5 lines) in tests/test_sync_sessions.py:424
info Commented-code block (5 lines) in scripts/apply-decay.py:95
info Commented-code block (8 lines) in scripts/lit-scout-zotero-import.py:112
info Commented-code block (6 lines) in scripts/bulk-archive.py:236
info Commented-code block (5 lines) in scripts/zotero.py:383
info Commented-code block (6 lines) in scripts/rebuild-postgres.py:92
info Commented-code block (6 lines) in scripts/fetch-memories.py:773
info Commented-code block (12 lines) in scripts/resample-bake-off-manifest.py:387

View all commented-out code 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/bb803ddd-580b-47f4-ac7a-c1ea6931b4f0/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/bb803ddd-580b-47f4-ac7a-c1ea6931b4f0/

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.