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.

Ddundee/forge

https://github.com/Ddundee/forge · scanned 2026-06-17 01:26 UTC (1 month, 2 weeks ago)

19 raw signals (0 security + 19 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

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

JSON

77.8% cov · 18 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

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

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 62.2/100 with 77.8% coverage. It contains 493 nodes across 1 cross-layer flows, written primarily in mixed languages. Engine surfaced 19 findings — concentrated in security (8), frontend (7), cicd (3). Risk profile is high: 1 critical, 2 high, 6 medium. Recommended next step: open the security layer findings first — that's where the highest-impact wins live.

Showing 17 of 18 actionable findings. 19 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/agents/deploy.ts:41

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

src/agents/deploy.ts:41 Exec used

high System graph security security conf 1.00 Insecure pattern 'exec_used' in src/tools/executor.ts:33

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

src/tools/executor.ts:33 Exec used

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.yml CI/CD securitySupply chainGithub actions

medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/agents/deploy.ts:1

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

src/agents/deploy.ts:1 Node child process

medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/codexDriver.ts:1

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

src/codexDriver.ts:1 Node child process

medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/commands/attach.ts:3

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

src/commands/attach.ts:3 Node child process

medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/skills/cli.ts:1

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

src/skills/cli.ts:1 Node child process

medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/tools/executor.ts:1

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

src/tools/executor.ts:1 Node child process

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

Found 47 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 2 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, 2 locations

.github/workflows/release.yml:16

.github/workflows/test.yml:16

CI/CD securitySupply chainGithub actions

low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — src/cli.ts:74