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.

RasmusTho/agentic-pkm-mvp

https://github.com/RasmusTho/agentic-pkm-mvp · scanned 2026-06-15 23:47 UTC (2 months, 3 weeks ago)

276 raw signals (0 security + 276 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 2 months, 3 weeks ago · v1 · 232 actionable findings from 1 signal source. 44 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 · 232 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 1 High 27 Medium 25 Low 144 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 232 Crowd 0 Layer: Software 21 Hardware 3 Frontend 1 Security 32 Cicd 2 Quality 123 Api 50

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

3 matching findings on this repo

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

View all duplicates & near-duplicates findings →

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

9 matching findings on this repo

low Old/deprecated-named symbol `test_pipeline_flag_off_matches_legacy` in tests/di…
low Old/deprecated-named symbol `auto_tag_legacy` in tests/components/embeddings/te…
low Old/deprecated-named symbol `auto_tag_legacy` in tests/components/embeddings/te…
low Old/deprecated-named symbol `test_known_providers_has_legacy` in tests/componen…
low Old/deprecated-named symbol `auto_tag_legacy` in tests/components/embeddings/te…
low Old/deprecated-named symbol `auto_tag_legacy` in tests/components/embeddings/ru…
low Old/deprecated-named symbol `store_stats_legacy` in app/cli/__init__.py:402
low Old/deprecated-named symbol `auto_tag_legacy` in app/components/embeddings/__in…
low Old/deprecated-named symbol `auto_tag_legacy` in app/components/embeddings/migr…

View all legacy markers findings →

Commented-out code 33 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 (5 lines) in tests/uat/test_negative_safety_integrated_run…
info Commented-code block (9 lines) in tests/api/test_companion_vault_routing.py:161
info Commented-code block (5 lines) in tests/companion_ui/test_receipts_history_surf…
info Commented-code block (5 lines) in tests/companion_ui/test_entry_state_gallery.p…
info Commented-code block (5 lines) in tests/companion_ui/test_workspace_read_only_p…
info Commented-code block (5 lines) in tests/companion_ui/test_overlay_host.py:336
info Commented-code block (7 lines) in tests/agents/panel_agent/test_panel_graph.py:…
info Commented-code block (6 lines) in tests/agents/panel_agent/test_panel_runtime.p…
info Commented-code block (6 lines) in tests/e2e/test_reality_mvp_pipeline.py:38
info Commented-code block (7 lines) in app/vault/settings_service.py:350
info Commented-code block (9 lines) in app/vault/manager.py:178
info Commented-code block (7 lines) in app/vault/actions.py:265

View all commented-out code findings →

Config drift 4 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.

4 matching findings on this repo

low Possibly dead Python function: configure_rate_limit_storage app/auth.py:31
info Commented-code block (7 lines) in app/config/__init__.py:1
low Old/deprecated-named symbol `model_copy` in app/config/agent.py:107
info Commented-code block (6 lines) in app/watcher/config.py:55

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/46803982-46fb-43f0-a877-76df0b68a0cb/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/46803982-46fb-43f0-a877-76df0b68a0cb/

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.