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.

skin306152-star/pearnly-app

https://github.com/skin306152-star/pearnly-app · scanned 2026-06-16 00:15 UTC (2 months, 2 weeks ago)

855 raw signals (0 security + 855 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

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

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 4 High 272 Medium 184 Low 197 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 809 Crowd 0 Layer: Software 13 Frontend 11 Hardware 3 Security 417 Cicd 1 Quality 303 Api 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 4 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.

4 matching findings on this repo

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

View all duplicates & near-duplicates findings →

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

6 matching findings on this repo

low Old/deprecated-named symbol `test_response_shape_is_rich_not_legacy` in tests/u…
low Old/deprecated-named symbol `_pipe_legacy` in routes/recon_routes_v1_batch.py:1…
low Old/deprecated-named symbol `_workspace_from_store_or_legacy` in routes/pos_aut…
low Old/deprecated-named symbol `bank_recon_v2` in services/recon/bank_stmt_legacy_…
low Old/deprecated-named symbol `bank_stmt_legacy` in services/recon/bank_stmt_lega…
low Old/deprecated-named symbol `is_copy` in services/ocr/legacy_adapter.py:16

View all legacy markers findings →

Commented-out code 150 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 app.py:336
info Commented-code block (5 lines) in eslint.config.mjs:3
info Commented-code block (5 lines) in tests/integration/test_mrerp_e2e_auto_sync.py…
info Commented-code block (5 lines) in tests/unit/test_mrerp_validate_history.py:214
info Commented-code block (5 lines) in tests/unit/test_erp_test_connection_route_dis…
info Commented-code block (5 lines) in tests/e2e/05-exceptions.spec.js:1
info Commented-code block (8 lines) in tests/e2e/13-password-change.spec.js:6
info Commented-code block (5 lines) in tests/e2e/11-charge-ocr-closure.spec.js:1
info Commented-code block (5 lines) in tests/e2e/08-erp-push.spec.js:1
info Commented-code block (8 lines) in tests/e2e/14-line-binding.spec.js:1
info Commented-code block (6 lines) in tests/e2e/03-clients.spec.js:1
info Commented-code block (14 lines) in tests/e2e/16-ocr-recognize.spec.js:1

View all commented-out code findings →

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

8 matching findings on this repo

info Commented-code block (5 lines) in eslint.config.mjs:3
high FastAPI POST `api_create_supplier` without auth dependency — routes/purchase_co… routes/purchase_config_routes.py:62
high FastAPI PATCH `api_update_supplier` without auth dependency — routes/purchase_c… routes/purchase_config_routes.py:87
high FastAPI DELETE `api_delete_supplier` without auth dependency — routes/purchase_… routes/purchase_config_routes.py:112
high FastAPI POST `api_create_category` without auth dependency — routes/purchase_co… routes/purchase_config_routes.py:149
high FastAPI PATCH `api_update_category` without auth dependency — routes/purchase_c… routes/purchase_config_routes.py:168
high FastAPI DELETE `api_delete_category` without auth dependency — routes/purchase_… routes/purchase_config_routes.py:188
high FastAPI PUT `api_save_settings` without auth dependency — routes/purchase_confi… routes/purchase_config_routes.py:224

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/fe8c17ea-929d-4c6b-ba1f-1087c9a7f6bf/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/fe8c17ea-929d-4c6b-ba1f-1087c9a7f6bf/

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.