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.

bprateeek/demoframe

https://github.com/bprateeek/demoframe · scanned 2026-06-17 01:42 UTC (1 month, 1 week ago)

13 raw signals (0 security + 13 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

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

JSON

77.8% cov · 13 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

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

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

Showing 13 of 13 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 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/readme-demo.yml CI/CD securitySupply chainGithub actions

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

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

src/encode/exec.ts:1 Node child process

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

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

src/mcp.ts:5 Node child process

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

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

src/qa/report.ts:3 Node child process

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

Found 42 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 frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — src/cli.ts:37