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.

selhorys/dataspoke-baseline

https://github.com/selhorys/dataspoke-baseline · scanned 2026-06-16 00:06 UTC (2 months, 2 weeks ago)

227 raw signals (9 security + 218 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 2 months, 2 weeks ago · v1 · 205 actionable findings from 2 signal sources. 176 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 · 197 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 3 High 28 Medium 18 Low 91 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 8 System graph 197 Crowd 0 Layer: Quality 103 Security 28 Software 8 Frontend 8 Hardware 7 Cicd 1 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 repo-level

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 Docker base image is tag-pinned but not digest-pinned: bitnamilegacy/postgresql… docker-images/postgres/Dockerfile:69

View all legacy markers findings →

Commented-out code 60 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 tests/integration/api_wired/test_uc1_02_activ…
info Commented-code block (5 lines) in tests/integration/api_wired/test_uc2_01_valid…
info Commented-code block (6 lines) in tests/integration/api_wired/test_uc1_03_passi…
info Commented-code block (7 lines) in tests/integration/api_wired/test_uc5_01_gover…
info Commented-code block (6 lines) in tests/integration/api_wired/test_uc4_01_metad…
info Commented-code block (8 lines) in tests/integration/api_wired/test_uc1_01_datah…
info Commented-code block (5 lines) in tests/integration/spot/test_auth_role_sync_da…
info Commented-code block (5 lines) in tests/integration/spot/test_validation_list_v…
info Commented-code block (5 lines) in tests/integration/spot/test_admin.py:223
info Commented-code block (5 lines) in tests/integration/spot/test_validation_passiv…
info Commented-code block (6 lines) in tests/integration/spot/test_ingestion_sources…
info Commented-code block (5 lines) in tests/unit/api/routers/spoke/test_validation.…

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 Agent instruction/config may expose a secret: .claude/agent-memory/test-reviewe… .claude/agent-memory/test-reviewer/project_recipe…:2
high Agent instruction/config may expose a secret: .claude/skills/datahub-api/SKILL.… .claude/skills/datahub-api/SKILL.md:121
low Old/deprecated-named symbol `idx_old` in tests/unit/shared/datahub/test_consume…
info Commented-code block (5 lines) in tests/unit/shared/datahub/test_consumer_recon…
low Old/deprecated-named symbol `existing_v2` in tests/unit/backend/admin/test_conf…
info Commented-code block (7 lines) in tests/unit/backend/admin/test_config_service.…
info Commented-code block (5 lines) in src/shared/notifications/config.py:1

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/b404da01-70b3-49aa-96e1-2a2006063a1e/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/b404da01-70b3-49aa-96e1-2a2006063a1e/

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.