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.

TOOTRJ/cardforge

https://github.com/TOOTRJ/cardforge · scanned 2026-06-16 00:40 UTC (2 months, 1 week ago)

271 raw signals (81 security + 190 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 2 months, 1 week ago · v1 · 198 actionable findings from 2 signal sources. 183 repeated signals grouped for readability. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON

100.0% cov · 190 findings

Severity distribution — click a segment to filter

Active filters: severity: low × excluding tests × Reset all

Severity: Critical 2 High 3 Medium 24 Low 7 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 8 System graph 190 Crowd 0 Layer: Quality 165 Security 7 Api 1 Frontend 24 Cicd 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 65.7/100 with 100.0% coverage. It contains 1566 nodes across 6 cross-layer flows, written primarily in mixed languages. Engine surfaced 190 findings — concentrated in quality (158), frontend (24), security (6). Risk profile is low: 0 critical, 0 high, 21 medium. Recommended next step: open the quality layer findings first — that's where the highest-impact wins live.

Showing 7 of 198 actionable findings. 381 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.

low System graph quality Integrity conf 1.00 7 env vars used in code but missing from .env.example

Drift between code and config docs. The first few: `BATCH`, `CI`, `HARNESS_URL`, `NODE_ENV`, `REBAKE_URL`, `VERCEL_PROJECT_PRODUCTION_URL`, `VERCEL_URL`. Add them (with a placeholder/comment) to .env.example so onboarding doesn't break.

config drift

low System graph quality Production readiness conf 1.00 Composite production-readiness gap

Multiple low-cost hardening controls are missing together: license, ci. Opus verification showed these co-occurring gaps are a better readiness signal than reading each flag in isolation.

Repo hardeningGenerated repo pattern

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

Found 23 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 quality Tests conf 1.00 Low test-to-source ratio

32 tests / 290 src (ratio 0.11).

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 frontend Frontend quality conf 1.00 React Flow edge with `label=` but no project-wide edge-label CSS override — components/creator/panels/frame-panel.tsx:55

React Flow edge labels render with a white rectangle behind the text by default, which scatters bright boxes across a dark canvas. Either drop the label, or override `.react-flow__edge-textbg` and `.react-flow__edge-text` in your stylesheet. Why: P-H in CHECKLIST.md — vendor edge labels bleed whit…

Fq edge label no bg

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

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/8c4b30e5-a95c-4075-a13e-233bd0857a74/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/8c4b30e5-a95c-4075-a13e-233bd0857a74/

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.