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.

raphaelfh/prumo

https://github.com/raphaelfh/prumo · scanned 2026-06-15 23:47 UTC (2 months, 4 weeks ago)

284 raw signals (0 security + 284 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

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

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 4 High 17 Medium 31 Low 81 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 241 Crowd 0 Layer: Software 12 Frontend 32 Hardware 4 Security 22 Cicd 2 Quality 129 Api 40

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 3 places repo-level
low Near-duplicate function bodies in 2 places repo-level
low Near-duplicate function bodies in 7 places

View all duplicates & near-duplicates findings →

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 `baseline_v1` in scripts/fitness/check_legacy_conce…
low Old/deprecated-named symbol `useLegacy` in backend/tests/unit/scripts/test_chec…
low Old/deprecated-named symbol `extraction_legacy` in backend/tests/unit/scripts/t…

View all legacy markers findings →

Commented-out code 75 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 playwright.config.ts:96
info Commented-code block (5 lines) in vitest.config.ts:8
info Commented-code block (7 lines) in frontend/integrations/api/client.ts:135
info Commented-code block (5 lines) in frontend/pdf-viewer/PrumoPdfViewer.tsx:46
info Commented-code block (8 lines) in frontend/pdf-viewer/primitives/Viewer.tsx:50
info Commented-code block (7 lines) in frontend/test/rls-section-field.test.ts:77
info Commented-code block (8 lines) in frontend/test/hooks/useAutoSaveProposals.test…
info Commented-code block (7 lines) in frontend/test/hooks/useExtractedValues.test.t…
info Commented-code block (6 lines) in frontend/test/hooks/useModelManagement.test.t…
info Commented-code block (5 lines) in frontend/components/ui/resizable-panel.tsx:117
info Commented-code block (5 lines) in frontend/components/runs/ReviewerAvatarStack.…
info Commented-code block (8 lines) in frontend/components/extraction/ArticleExtract…

View all commented-out code findings →

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

9 matching findings on this repo

info Commented-code block (5 lines) in playwright.config.ts:96
info Commented-code block (5 lines) in vitest.config.ts:8
info Commented-code block (5 lines) in backend/app/core/config.py:42
low Unused endpoint: GET /projects/{project_id}/hitl-config
low Unused endpoint: PUT /projects/{project_id}/hitl-config
low Unused endpoint: DELETE /projects/{project_id}/hitl-config
low Unused endpoint: GET /projects/{project_id}/templates/{project_template_id}/hit…
low Unused endpoint: PUT /projects/{project_id}/templates/{project_template_id}/hit…
low Unused endpoint: DELETE /projects/{project_id}/templates/{project_template_id}/…

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/baa64971-68cb-4924-958a-06febe4d52bd/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/baa64971-68cb-4924-958a-06febe4d52bd/

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.