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.

sjhennig/claude-scaffold

https://github.com/sjhennig/claude-scaffold · scanned 2026-06-16 00:14 UTC (2 months, 2 weeks ago)

44 raw signals (0 security + 44 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 2 months, 2 weeks ago · v1 · 31 actionable findings from 1 signal source. 13 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 · 31 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 0 High 1 Medium 8 Low 7 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 31 Crowd 0 Layer: Frontend 3 Hardware 2 Security 7 Cicd 3 Quality 16

Exclude dismissed / FP Exclude test files

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 46.8/100 with 66.7% coverage. It contains 214 nodes across 0 cross-layer flows, written primarily in mixed languages. Engine surfaced 44 findings — concentrated in cicd (16), quality (16), security (7). Risk profile is high: 0 critical, 1 high, 9 medium. Recommended next step: open the cicd layer findings first — that's where the highest-impact wins live.

Showing 13 of 31 actionable findings. 44 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.

high System graph security security conf 1.00 Insecure pattern 'exec_used' in src/doctor.js:255

Found a known-risky pattern (exec_used). Review and replace if possible.

src/doctor.js:255 Exec used

medium System graph cicd CI/CD security conf 1.00 2 occurrences GitHub Action is tag-pinned rather than SHA-pinned

github/codeql-action/init@v3 can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.

lines 27, 32

.github/workflows/codeql.yml:27, 32 (2 hits)

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 scripts/agent-smoke.mjs:45

Found a known-risky pattern (node_child_process). Review and replace if possible.

scripts/agent-smoke.mjs:45 Node child process

medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/doctor.js:14

Found a known-risky pattern (node_child_process). Review and replace if possible.

src/doctor.js:14 Node child process

medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/index.js:3

Found a known-risky pattern (node_child_process). Review and replace if possible.

src/index.js:3 Node child process

low System graph hardware Coverage conf 1.00 Containers defined but no K8s/orchestration manifest found

Repo has Dockerfiles/compose but no Kubernetes/Nomad manifests. If the target deployment is K8s, the manifests may live in a separate ops repo.

Deployment

low System graph quality Debug conf 1.00 Debug logging residue appears in source files

Found 19 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 hardware Supply chain conf 1.00 Docker base image is tag-pinned but not digest-pinned: node:20-bookworm-slim

Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.

.devcontainer/Dockerfile:1 containersPinned dependencies

low System graph cicd CI/CD security conf 1.00 13 occurrences GitHub Action is tag-pinned rather than SHA-pinned

actions/checkout@v5 can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.

4 files, 13 locations

.github/workflows/ci.yml:29, 32, 68, 75, 97, 102, 128, 135 (8 hits)

.github/workflows/dependency-review.yml:16, 19 (2 hits)

.github/workflows/publish.yml:32, 39 (2 hits)

.github/workflows/codeql.yml:24

CI/CD securitySupply chainGithub actions

low System graph quality Provenance conf 1.00 Shallow git history limits provenance confidence

The repository is a shallow clone. Origin/evolution analysis cannot distinguish fresh generation, imported legacy code, or long-lived human code with high confidence.

Git historyGenerated repo pattern

low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — src/index.js:152

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 — src/templates/project-files.js:428

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

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/0bc56789-a460-434e-a72f-b2e474d25738/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/0bc56789-a460-434e-a72f-b2e474d25738/

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.