florianfesti/boxes

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.

101 of your 129 findings came from Repobility's proprietary detections. ✓ Repobility tags below mark them.

Upstream (GitHub) caused delay on this scan — not Repobility.

GitHub API rate-limited (HTTP 403) — preflight skipped, fell back to direct git clone.
Clone from GitHub took 41.11s for a 54.3 MB repo slow.
Repobility's analysis ran in 5.87s after the clone landed.

https://github.com/florianfesti/boxes · scanned 2026-06-05 20:13 UTC (4 days, 14 hours ago) · 10 languages

285 raw signals (125 security + 160 graph) 11/13 scanners ran 63rd percentile · Python · medium (20-100K LoC) System graph score 79 (lower by 8)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 4 days, 14 hours ago · v2 · 88 actionable findings from 2 signal sources. 117 repeated signals grouped for readability. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON

88.9% cov · 58 findings

Score breakdown â 2026-05-18-v5

Component	Sub-score	Weight	Contribution
`structure_score`	75.0	0.15	11.25
`security_score`	100.0	0.25	25.00
`testing_score`	25.0	0.20	5.00
`documentation_score`	86.0	0.15	12.90
`practices_score`	79.0	0.15	11.85
`code_quality`	58.0	0.10	5.80
Overall		1.00	71.8

security_score may be inflated — optional security scanners were skipped on this fast scan

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 0 High 11 Medium 15 Low 45 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 30 System graph 58 Crowd 0 Layer: Software 29 Quality 38 Cicd 11 Security 3 Api 1 Frontend 2 Hardware 4

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 5 places

View all duplicates & near-duplicates findings →

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

7 matching findings on this repo

info Commented-code block (5 lines) in tests/test_svg.py:50
info Commented-code block (6 lines) in static/self.js:135
info Commented-code block (17 lines) in boxes/gears.py:20
info Commented-code block (5 lines) in boxes/generators/gridfinitytraylayout.py:151
info Commented-code block (12 lines) in boxes/generators/_template.py:27
info Commented-code block (7 lines) in boxes/generators/halfbox.py:51
info Commented-code block (5 lines) in boxes/generators/jigsaw.py:72

View all commented-out code findings →

Config drift 1 finding

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.

1 matching finding on this repo

high [MINED131] pre-commit hook `https://github.com/pre-commit/pre-commit-hooks` pin… .pre-commit-config.yaml:8

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/57162b1e-634b-42c9-b6ff-6f3bc90ba2fd/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/57162b1e-634b-42c9-b6ff-6f3bc90ba2fd/

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.