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

color4pen/spec-runner

https://github.com/color4pen/spec-runner · scanned 2026-06-17 01:55 UTC (1 month, 1 week ago)

46 raw signals (0 security + 46 graph)

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

Complete repo analysis

Last scanned 1 month, 1 week ago · v2 · last Δ -14.9 (diff) · 46 actionable findings from 1 signal source. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON
Combined
61.8
/100
Security checks
62
0 findings
System graph
62
77.8% cov · 46 findings
Critical
2
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 2 High 0 Medium 14 Low 7 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 46 Crowd 0 Layer: Security 10 Cicd 2 Quality 34
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 61.8/100 with 77.8% coverage. It contains 7827 nodes across 20 cross-layer flows, written primarily in mixed languages. Engine surfaced 46 findings — concentrated in quality (34), security (10), cicd (2). Risk profile is high: 2 critical, 0 high, 14 medium. Recommended next step: open the quality layer findings first — that's where the highest-impact wins live.

Showing 19 of 46 actionable findings. 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 — src/core/doctor/checks/auth/managed-key-valid.ts:4
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 Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — src/git/__tests__/transport-auth.test.ts:520
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 Placeholder conf 1.00 Critical user flow still appears backed by mock or placeholder data
A payment/auth/admin/order/billing-style flow contains mock, fake, TODO, dummy, or placeholder markers in runtime source. In the Fable corpus this is a high-leverage completeness smell: the app can look finished while the money, identity, or tenant flow is still scaffolded.
Mock dataCritical flowGenerated repo pattern
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/release-please.yml 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/publish.yml CI/CD securitySupply chainGithub actions
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/cli/doctor.ts:9
Found a known-risky pattern (node_child_process). Review and replace if possible.
src/cli/doctor.ts:9 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/core/verification/commands.ts:7
Found a known-risky pattern (node_child_process). Review and replace if possible.
src/core/verification/commands.ts:7 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/git/dynamic-context.ts:10
Found a known-risky pattern (node_child_process). Review and replace if possible.
src/git/dynamic-context.ts:10 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/git/remote.ts:1
Found a known-risky pattern (node_child_process). Review and replace if possible.
src/git/remote.ts:1 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/git/transport-auth.ts:11
Found a known-risky pattern (node_child_process). Review and replace if possible.
src/git/transport-auth.ts:11 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/util/git-exec.ts:1
Found a known-risky pattern (node_child_process). Review and replace if possible.
src/util/git-exec.ts:1 Node child process
medium System graph quality Placeholder conf 1.00 Placeholder or mock-heavy implementation detected
Found 13 placeholder/mock markers across 12 source files. This often means the repo looks complete while core flows still use generated scaffolding or fake data.
Mock dataIncompleteGenerated repo pattern
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `agent_old` in tests/unit/config/migrate.test.ts:104
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 `draftPathLegacy` in src/util/paths.ts:152
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 `draftPathLegacy` in tests/unit/util/paths.test.ts:5
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 Complexity conf 1.00 Very large file: tests/pipeline-integration.test.ts (1676 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: tests/unit/adapter/claude-code/agent-runner.test.ts (2951 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: tests/unit/adapter/managed-agent/agent-runner.test.ts (2022 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: tests/unit/step/executor.test.ts (1328 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/f271b73b-ef37-4e93-899c-105e38cdc02c/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/f271b73b-ef37-4e93-899c-105e38cdc02c/

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.