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.

Thomas-AppForceOne/ClaudeAgents

https://github.com/Thomas-AppForceOne/ClaudeAgents · scanned 2026-06-16 01:14 UTC (2 months, 1 week ago)

251 raw signals (38 security + 213 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 2 months, 1 week ago · v2 · 221 actionable findings from 2 signal sources. 78 repeated signals grouped for readability. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON

66.7% cov · 213 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 2 High 5 Medium 22 Low 7 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 8 System graph 213 Crowd 0 Layer: Quality 202 Security 17 Frontend 1 Cicd 1

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.

Commented-out code 184 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 (8 lines) in tests/hook-probe/probe.test.ts:48
info Commented-code block (5 lines) in tests/safety/check-role-ceiling.test.ts:99
info Commented-code block (8 lines) in tests/safety/recovery.test.ts:169
info Commented-code block (8 lines) in tests/safety/fingerprint.test.ts:1
info Commented-code block (17 lines) in tests/safety/config.test.ts:1
info Commented-code block (6 lines) in tests/safety/oscillation.test.ts:329
info Commented-code block (6 lines) in tests/trace/concurrent-append.test.ts:105
info Commented-code block (5 lines) in tests/trace/independent-review-event-three-pl…
info Commented-code block (6 lines) in tests/trace/reconcile-tool.test.ts:158
info Commented-code block (5 lines) in tests/trace/aggregate-sprint-summary-counts-r…
info Commented-code block (12 lines) in tests/config-server/overlay-telemetry.test.t…
info Commented-code block (11 lines) in tests/config-server/q5-documentation-schema.…

View all commented-out code findings →

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

medium Insecure pattern 'node_child_process' in src/config-server/tools/writes.ts:27 src/config-server/tools/writes.ts:27
medium Insecure pattern 'node_child_process' in src/config-server/tools/independent-re… src/config-server/tools/independent-review.ts:44
medium Insecure pattern 'node_child_process' in src/config-server/storage/git-exec.ts:… src/config-server/storage/git-exec.ts:11
medium Insecure pattern 'node_child_process' in src/config-server/storage/module-loade… src/config-server/storage/module-loader.ts:24
medium Insecure pattern 'node_child_process' in src/config-server/storage/module-state… src/config-server/storage/module-state-store.ts:21
high Insecure pattern 'exec_used' in src/config-server/storage/run-store.ts:98 src/config-server/storage/run-store.ts:98
medium Insecure pattern 'node_child_process' in src/config-server/storage/run-store.ts… src/config-server/storage/run-store.ts:17
low Very large file: tests/config-server/tools/writes.test.ts (1611 lines)
low Very large file: src/config-server/index.ts (2579 lines)
info Commented-code block (17 lines) in tests/safety/config.test.ts:1
info Commented-code block (12 lines) in tests/config-server/overlay-telemetry.test.t…
info Commented-code block (11 lines) in tests/config-server/q5-documentation-schema.…

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/7966b8b8-2b5d-466d-91e1-7122c7513e34/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/7966b8b8-2b5d-466d-91e1-7122c7513e34/

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.