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.
Sign up free Scan another repo

adam-jackson-cf/raidar

https://github.com/adam-jackson-cf/raidar · scanned 2026-06-17 01:29 UTC (1 month, 2 weeks ago)

75 raw signals (0 security + 75 graph)

File as issue Image
UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 1 month, 2 weeks ago · v2 · last Δ -21.4 (diff) · 67 actionable findings from 1 signal source. 8 repeated signals grouped for readability. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON
Combined
55.3
/100
Security checks
55
0 findings
System graph
55
88.9% cov · 67 findings
Critical
0
click to filter
Agents
10
0 votes
Crowd
0
reported
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all
Severity: Critical 0 High 0 Medium 24 Low 38 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 67 Crowd 0 Layer: Software 10 Api 1 Frontend 12 Security 5 Cicd 3 Quality 36
Corpus Intelligence Cross-corpus context (cohort percentile, top patterns, fix plan) is shown only on repositories you own. Sign up and connect your repo to view it.
Scan summary Repository scanned at 55.3/100 with 88.9% coverage. It contains 2765 nodes across 7 cross-layer flows, written primarily in mixed languages. Engine surfaced 75 findings — concentrated in quality (40), frontend (12), software (10). Risk profile is low: 0 critical, 0 high, 24 medium. Recommended next step: open the quality layer findings first — that's where the highest-impact wins live.

Showing 62 of 67 actionable findings. 75 raw detector signals were grouped into reader-sized issues. Click TP / FP to vote on a finding's accuracy — votes adjust the confidence weighting and improve detection across the platform.

medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — review-surface/src/api/client.ts:12
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: scenarios/bugfix-ledger-balance/v001/rules/AGENTS.md
This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.
scenarios/bugfix-ledger-balance/v001/rules/AGENTS.md VerificationAgents md
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: scenarios/bugfix-ledger-balance/v001/rules/CLAUDE.md
This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.
scenarios/bugfix-ledger-balance/v001/rules/CLAUDE.md VerificationClaude instruction
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: scenarios/bugfix-ledger-balance/v001/rules/copilot-instructions.md
This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.
scenarios/bugfix-ledger-balance/v001/rules/copilot-instructions.md VerificationAgent instruction
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: scenarios/bugfix-ledger-balance/v001/rules/GEMINI.md
This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.
scenarios/bugfix-ledger-balance/v001/rules/GEMINI.md VerificationGemini instruction
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: scenarios/homepage-implementation/v002/rules/AGENTS.md
This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.
scenarios/homepage-implementation/v002/rules/AGENTS.md VerificationAgents md
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: scenarios/homepage-implementation/v002/rules/CLAUDE.md
This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.
scenarios/homepage-implementation/v002/rules/CLAUDE.md VerificationClaude instruction
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: scenarios/homepage-implementation/v002/rules/copilot-instructions.md
This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.
scenarios/homepage-implementation/v002/rules/copilot-instructions.md VerificationAgent instruction
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: scenarios/homepage-implementation/v002/rules/GEMINI.md
This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.
scenarios/homepage-implementation/v002/rules/GEMINI.md VerificationGemini instruction
medium System graph quality Agent instructions conf 1.00 Agent instructions exist but release-hardening basics are missing
AI-coder instruction files were found, but the repo is missing license. Treat this as a contract gap: the agent is guided, but the generated output is not yet guarded by the controls that make it repeatable.
Repo hardeningGenerated repo pattern
medium System graph quality Integrity conf 1.00 Frontend route `/runs/:runId` has no Link/navigate to it — review-surface/src/router.tsx
The route is registered but no `<Link to=…>` or `navigate(…)` in the codebase navigates here. Either it's reachable only via direct URL (intentional), it's dead, or the link broke during a refactor.
Orphan pageWiring
medium System graph cicd CI/CD security conf 1.00 GitHub Action is tag-pinned rather than SHA-pinned
oven-sh/setup-bun@v2 can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.
.github/workflows/ci-quality-gates-incremental.yml:28 CI/CD securitySupply chainGithub actions
medium System graph cicd CI/CD security conf 1.00 GitHub Actions workflow grants broad write permissions
CI tokens with write permissions increase blast radius when an action, dependency, or PR workflow is compromised. Prefer job-level least-privilege permissions.
.github/workflows/version-changelog.yml CI/CD securitySupply chainGithub actions
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in orchestrator/src/raidar/assets/verifier-score-scenario.mjs:2
Found a known-risky pattern (node_child_process). Review and replace if possible.
orchestrator/src/raidar/assets/verifier-score-scenario.mjs:2 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scenarios/bugfix-ledger-balance/v001/starter/scripts/capture-screenshot.ts:2
Found a known-risky pattern (node_child_process). Review and replace if possible.
scenarios/bugfix-ledger-balance/v001/starter/scripts/capture-screenshot.ts:2 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scenarios/hello-world-smoke/v001/starter/scripts/capture-screenshot.ts:2
Found a known-risky pattern (node_child_process). Review and replace if possible.
scenarios/hello-world-smoke/v001/starter/scripts/capture-screenshot.ts:2 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scenarios/homepage-implementation/v001/starter/scripts/capture-screenshot.ts:2
Found a known-risky pattern (node_child_process). Review and replace if possible.
scenarios/homepage-implementation/v001/starter/scripts/capture-screenshot.ts:2 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scenarios/homepage-implementation/v002/starter/scripts/capture-screenshot.ts:2
Found a known-risky pattern (node_child_process). Review and replace if possible.
scenarios/homepage-implementation/v002/starter/scripts/capture-screenshot.ts:2 Node child process
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — orchestrator/src/raidar/application/repo_state.py:14
`subprocess.run(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — orchestrator/src/raidar/commands/env_harbor.py:80
`subprocess.run(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — orchestrator/src/raidar/commands/harness.py:108
`subprocess.run(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — orchestrator/src/raidar/scenario_clone.py:125
`subprocess.run(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — scripts/checks/check-python-fanout.py:71
`subprocess.run(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — scripts/release/bump-version.py:114
`subprocess.run(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.
runtime safetyRobustness
low System graph quality Integrity conf 1.00 8 env vars used in code but missing from .env.example
Drift between code and config docs. The first few: `CI`, `CODEX_CLI_PATH`, `CODEX_HOME`, `NEXT_TELEMETRY_DISABLED`, `PYTHONPATH`, `RAIDAR_APP_DIR`, `RAIDAR_LOG_DIR`, `REVIEW_SURFACE_PORT`. Add them (with a placeholder/comment) to .env.example so onboarding doesn't break.
config drift
low System graph quality Debug conf 1.00 Debug logging residue appears in source files
Found 52 console/debugger/print-style debug statements in non-test source. This is a common fast-generation residue before production cleanup.
CleanupRepo hardeningGenerated repo pattern
low System graph cicd CI/CD security conf 1.00 5 occurrences GitHub Action is tag-pinned rather than SHA-pinned
actions/checkout@v4 can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.
2 files, 5 locations
.github/workflows/version-changelog.yml:19, 25, 30 (3 hits)
.github/workflows/ci-quality-gates-incremental.yml:15, 18 (2 hits)
CI/CD securitySupply chainGithub actions
low System graph quality Integrity conf 1.00 4 occurrences Near-duplicate function bodies in 2 places
Functions with the same first-5-line body hash: scripts/checks/check-python-quality.py:structure_diagnostics_for_relpath, scripts/checks/check-python-quality.py:structure_diagnostics This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — see https://jw.hn/ai-code-hygiene). …
4 occurrences
repo-level (4 hits)
duplicatesduplication
low System graph quality Integrity conf 1.00 2 occurrences Near-duplicate function bodies in 3 places
Functions with the same first-5-line body hash: orchestrator/src/raidar/agents/harbor_agents/cli_agents.py:name, orchestrator/src/raidar/agents/harbor_agents/cli_agents.py:name, orchestrator/src/raidar/agents/harbor_agents/cli_agents.py:name This is *the* AI-coder failure mode (4× more duplication…
2 occurrences
repo-level (2 hits)
duplicatesduplication
low System graph quality Integrity conf 1.00 Near-duplicate function bodies in 4 places
Functions with the same first-5-line body hash: orchestrator/src/raidar/schemas/scorecard.py:score, orchestrator/src/raidar/schemas/scorecard.py:score, orchestrator/src/raidar/schemas/scorecard.py:score, orchestrator/src/raidar/schemas/scorecard.py:score This is *the* AI-coder failure mode (4× mor…
duplicatesduplication
low System graph quality License conf 1.00 No license file detected
No LICENSE/COPYING/NOTICE file was found. Generated repositories often omit licensing, which blocks reuse and automated intake.
Repo hardeningGenerated repo pattern
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `large_old` in orchestrator/tests/test_task_image_cache_behaviors.py:59
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `lint_unused` in orchestrator/src/raidar/schemas/events.py:41
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `model_copy` in orchestrator/src/raidar/findings.py:95
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `model_copy` in orchestrator/src/raidar/runtime/scorecard.py:479
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `model_copy` in orchestrator/src/raidar/runtime/scoring_outputs.py:110
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `model_copy` in orchestrator/src/raidar/scorers/plan_to_code.py:119
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `model_copy` in orchestrator/src/raidar/scorers/registry.py:70
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `model_copy` in orchestrator/tests/test_storage.py:49
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `test_categorizes_lint_unused` in orchestrator/tests/test_gate_watcher.py:19
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph software Dead code conf 1.00 Possibly dead Python function: decorator
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
orchestrator/src/raidar/scorers/base.py:107
low System graph software Dead code conf 1.00 Possibly dead Python function: load_scenario_document
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
orchestrator/src/raidar/application/scenarios.py:209
low System graph software Dead code conf 1.00 Possibly dead Python function: parse_docker_compose_version
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
orchestrator/src/raidar/runtime/harbor.py:28
low System graph software Dead code conf 1.00 Possibly dead Python function: registered_scorers
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
orchestrator/src/raidar/scorers/base.py:128
low System graph software Dead code conf 1.00 Possibly dead Python function: resolve_scenario_relative_file
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
orchestrator/src/raidar/scenario_paths.py:55
low System graph software Dead code conf 1.00 Possibly dead Python function: scenario_revision_sort_key
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
orchestrator/src/raidar/application/scenarios.py:192
low System graph software Dead code conf 1.00 Possibly dead Python function: update_changelog
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
scripts/release/bump-version.py:256
low System graph software Dead code conf 1.00 Possibly dead Python function: validate_public_base_images
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
orchestrator/src/raidar/runtime/harbor.py:53
low System graph software Dead code conf 1.00 Possibly dead Python function: validate_scenario_relative_path
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
orchestrator/src/raidar/scenario_paths.py:29
low System graph software Dead code conf 1.00 Possibly dead Python function: validate_scorer_relative_path
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
orchestrator/src/raidar/scorers/paths.py:16
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — scenarios/bugfix-ledger-balance/v001/starter/scripts/capture-screenshot.ts:62
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — scenarios/hello-world-smoke/v001/starter/scripts/capture-screenshot.ts:62
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — scenarios/homepage-implementation/v001/reference/capture-reference.ts:31
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — scenarios/homepage-implementation/v001/starter/scripts/capture-screenshot.ts:125
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — scenarios/homepage-implementation/v002/reference/capture-reference.ts:31
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — scenarios/homepage-implementation/v002/starter/scripts/capture-screenshot.ts:125
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — scenarios/skill-benchmark-coding-test/v001/starter/scripts/capture-screenshot.ts:62
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — scenarios/skill-benchmark-coding-test/v002/starter/scripts/capture-screenshot.ts:62
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — scenarios/skill-benchmark-coding-test/v003/starter/scripts/capture-screenshot.ts:62
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph quality Integrity conf 1.00 Stub function `version` (body is just `pass`/`return`) — orchestrator/src/raidar/agents/harbor_agents/cli_agents.py:33
Likely an AI scaffold that was never filled in. Remove or implement.
Empty handlerDead code
low System graph quality Complexity conf 1.00 Very large file: orchestrator/tests/test_cli_commands.py (1531 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: orchestrator/tests/test_runner_metrics.py (2394 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
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/b32aa5d4-f111-49a5-9e87-6d33b89cadb2/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/b32aa5d4-f111-49a5-9e87-6d33b89cadb2/

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.