sartography/spiff-arena

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.

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

Scan timing: clone 29.89s · analysis 7.95s · 41.6 MB · GitHub API rate-limit (preflight)

https://github.com/sartography/spiff-arena · scanned 2026-06-05 19:16 UTC (4 days, 17 hours ago) · 10 languages

660 raw signals (216 security + 444 graph) 11/13 scanners ran 86th percentile · Python · large (100-500K LoC) System graph score 57 (higher by 30)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 4 days, 17 hours ago · v2 · 234 actionable findings from 2 signal sources. 179 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 · 156 findings

Score breakdown â 2026-05-18-v5

Component	Sub-score	Weight	Contribution
`structure_score`	60.0	0.15	9.00
`security_score`	100.0	0.25	25.00
`testing_score`	100.0	0.20	20.00
`documentation_score`	76.0	0.15	11.40
`practices_score`	94.0	0.15	14.10
`code_quality`	71.0	0.10	7.10
Overall		1.00	86.6

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 1 High 16 Medium 26 Low 102 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 78 System graph 156 Crowd 0 Layer: Quality 124 Cicd 18 Software 40 Security 5 Frontend 18 Network 6 Hardware 11 Api 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 5 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.

5 matching findings on this repo

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

View all duplicates & near-duplicates findings →

Legacy markers 1 finding

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.

1 matching finding on this repo

low Old/deprecated-named symbol `human_tasks_legacy` in spiffworkflow-backend/src/s…

View all legacy markers findings →

Commented-out code 29 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 (21 lines) in spiffworkflow-backend/tests/spiffworkflow_ba…
info Commented-code block (6 lines) in spiffworkflow-backend/tests/spiffworkflow_bac…
info Commented-code block (5 lines) in spiffworkflow-backend/tests/spiffworkflow_bac…
info Commented-code block (7 lines) in spiffworkflow-backend/migrations/versions/343…
info Commented-code block (5 lines) in spiffworkflow-backend/src/spiffworkflow_backe…
info Commented-code block (5 lines) in spiffworkflow-backend/src/spiffworkflow_backe…
info Commented-code block (16 lines) in spiffworkflow-backend/src/spiffworkflow_back…
info Commented-code block (5 lines) in spiffworkflow-backend/src/spiffworkflow_backe…
info Commented-code block (12 lines) in spiffworkflow-backend/src/spiffworkflow_back…
info Commented-code block (7 lines) in spiffworkflow-backend/src/spiffworkflow_backe…
info Commented-code block (8 lines) in spiffworkflow-backend/src/spiffworkflow_backe…
info Commented-code block (5 lines) in spiffworkflow-backend/src/spiffworkflow_backe…

View all commented-out code findings →

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

12 matching findings on this repo

high [MINED131] pre-commit hook `https://github.com/pre-commit/mirrors-prettier` pin… spiffworkflow-backend/.pre-commit-config.yaml:38
high [SEC027] XML External Entity (XXE) — Node.js xml parsers: Node.js XML parsers c… spiffworkflow-frontend/src/components/messages/Me…:50
low File has no detected symbols: spiffworkflow-backend/src/spiffworkflow_backend/c…
low File has no detected symbols: spiffworkflow-backend/src/spiffworkflow_backend/c…
low File has no detected symbols: spiffworkflow-frontend/vite.config.ts
low File has no detected symbols: spiffworkflow-frontend/eslint.config.js
low File has no detected symbols: spiffworkflow-frontend/vitest.config.ts
low File has no detected symbols: spiffworkflow-frontend/test/diagram_edit_acceptan…
info TODO/FIXME marker in shipping code — spiffworkflow-frontend/eslint.config.js:72
info Commented-code block (7 lines) in spiffworkflow-backend/src/spiffworkflow_backe…
info Commented-code block (5 lines) in spiffworkflow-frontend/vite.config.ts:13
medium Frontend route `secrets` has no Link/navigate to it — spiffworkflow-frontend/sr… repo-level

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/dcdaf7ef-267f-49f9-92a1-e14f4851e3ce/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/dcdaf7ef-267f-49f9-92a1-e14f4851e3ce/

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.