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.

benkirk/sam-queries

https://github.com/benkirk/sam-queries · scanned 2026-06-17 01:39 UTC (1 month, 2 weeks ago)

203 raw signals (0 security + 203 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 1 month, 2 weeks ago · v2 · last Δ -16.7 (diff) · 138 actionable findings from 1 signal source. 65 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 · 138 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 2 High 16 Medium 15 Low 45 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 138 Crowd 0 Layer: Software 18 Network 1 Hardware 5 Security 20 Cicd 5 Quality 89

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 7 places
low Near-duplicate function bodies in 8 places
low Near-duplicate function bodies in 4 places repo-level

View all duplicates & near-duplicates findings →

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

2 matching findings on this repo

low Old/deprecated-named symbol `expected_legacy` in tests/unit/test_accounting_mod…
low Old/deprecated-named symbol `n_deleted_legacy` in src/cli/accounting/commands.p…

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 (7 lines) in containers/sam-sql-dev/bootstrap_clone.py:252
info Commented-code block (5 lines) in tests/conftest.py:23
info Commented-code block (6 lines) in tests/factories/core.py:10
info Commented-code block (7 lines) in tests/api/test_schemas.py:31
info Commented-code block (7 lines) in tests/api/test_charge_endpoints.py:166
info Commented-code block (6 lines) in tests/unit/test_rate_limiter.py:173
info Commented-code block (5 lines) in tests/unit/test_webapp_jobs.py:1115
info Commented-code block (5 lines) in tests/unit/test_smoke.py:53
info Commented-code block (5 lines) in tests/unit/test_user_proj_usage.py:301
info Commented-code block (7 lines) in tests/unit/test_reconcile_quotas.py:892
info Commented-code block (5 lines) in tests/unit/test_sam_search_cli_allocations.py…
info Commented-code block (5 lines) in tests/unit/test_rbac.py:63

View all commented-out code findings →

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

6 matching findings on this repo

low Possibly dead Python function: cleanup_temp_config_files containers/sam-sql-dev/bootstrap_clone.py:70
medium Insecure pattern 'direct_innerhtml_assignment' in src/webapp/static/js/htmx-con… src/webapp/static/js/htmx-config.js:208
high Agent instruction/config may expose a secret: CLAUDE.md CLAUDE.md:694
info Commented-code block (8 lines) in src/webapp/config.py:63
info Commented-code block (5 lines) in src/webapp/static/js/htmx-config.js:31
info Commented-code block (5 lines) in src/webapp/utils/config_inspect.py:204

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/94dcbc29-0bd7-48c3-a632-2b99840e07e2/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/94dcbc29-0bd7-48c3-a632-2b99840e07e2/

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.