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.

andrewkatson/pos

https://github.com/andrewkatson/pos · scanned 2026-06-17 01:33 UTC (1 month, 2 weeks ago)

72 raw signals (0 security + 72 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 1 month, 2 weeks ago · v2 · last Δ +0.3 (diff) · 55 actionable findings from 1 signal source. 17 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 · 55 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 1 High 0 Medium 32 Low 14 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 55 Crowd 0 Layer: Software 11 Security 30 Cicd 2 Quality 12

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 1 finding

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.

1 matching finding on this repo

low Near-duplicate function bodies in 2 places

View all duplicates & near-duplicates findings →

Commented-out code 8 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/`.

8 matching findings on this repo

info Commented-code block (5 lines) in backend/user_system/admin.py:47
info Commented-code block (5 lines) in backend/user_system/views.py:1412
info Commented-code block (5 lines) in backend/user_system/models.py:74
info Commented-code block (5 lines) in backend/user_system/tests/test_like_comment_v…
info Commented-code block (5 lines) in backend/user_system/tests/test_login_remember…
info Commented-code block (5 lines) in backend/user_system/classifiers/classifier_co…
info Commented-code block (5 lines) in website/src/components/CharacterCounter.tsx:10
info Commented-code block (6 lines) in website/src/pages/PostDetailPage.tsx:94

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/31585043-3a2e-487a-941b-d4ac1ea6dcda/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/31585043-3a2e-487a-941b-d4ac1ea6dcda/

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.