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.

swarupd227/ACE

https://github.com/swarupd227/ACE · scanned 2026-06-16 00:27 UTC (2 months, 2 weeks ago)

172 raw signals (0 security + 172 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

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

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 0 High 68 Medium 13 Low 71 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 165 Crowd 0 Layer: Software 3 Frontend 10 Hardware 11 Security 72 Cicd 1 Quality 18 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 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 2 places repo-level
low Near-duplicate function bodies in 3 places

View all duplicates & near-duplicates findings →

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

4 matching findings on this repo

info Commented-code block (6 lines) in p2r/backend/app/sample.py:39
info Commented-code block (7 lines) in backend/app/pipeline/orchestrator.py:828
info Commented-code block (7 lines) in backend/app/seed/reference_data.py:2755
info Commented-code block (5 lines) in e2e/tests/demo.spec.js:1

View all commented-out code findings →

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

7 matching findings on this repo

high FastAPI PUT `admin_put_config` without auth dependency — p2r/backend/app/main.p… p2r/backend/app/main.py:416
high FastAPI POST `admin_reset_config` without auth dependency — p2r/backend/app/mai… p2r/backend/app/main.py:427
high FastAPI PUT `put_config` without auth dependency — backend/app/routes/admin.py:… backend/app/routes/admin.py:35
high FastAPI POST `reset_config` without auth dependency — backend/app/routes/admin.… backend/app/routes/admin.py:46
low Unused endpoint: GET /admin/config
low Unused endpoint: PUT /admin/config/{key}
low Unused endpoint: POST /admin/config/reset

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/6fdfa0a9-bc3b-4fa6-9c48-2b298f406ca2/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/6fdfa0a9-bc3b-4fa6-9c48-2b298f406ca2/

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.