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.

Crit-Fumble/cfg-foundry-plugin

https://github.com/Crit-Fumble/cfg-foundry-plugin · scanned 2026-06-17 01:24 UTC (1 month, 2 weeks ago)

40 raw signals (0 security + 40 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

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

JSON

88.9% cov · 40 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

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

Showing 30 of 40 actionable findings. Click TP / FP to vote on a finding's accuracy — votes adjust the confidence weighting and improve detection across the platform.

high System graph api Wiring conf 1.00 Dangling fetch: GET /api/game-data/${slug}/vtt-config (scripts/services/vtt-config-manager.js:103)

`scripts/services/vtt-config-manager.js:103` calls `GET /api/game-data/${slug}/vtt-config` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/game-data/<p>/vtt-config` If this points at an external API, prefix …

Dangling fetchHelper:request

high System graph api Wiring conf 1.00 Dangling fetch: POST /api/characters/validate (scripts/services/character-sync.js:125)

`scripts/services/character-sync.js:125` calls `POST /api/characters/validate` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/characters/validate` If this points at an external API, prefix it with `https://…

Dangling fetchHelper:request

medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — scripts/module.js:377

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 — scripts/views/cfg-campaign-links.js:259

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 security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in scripts/views/cfg-campaign-links.js:106

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

scripts/views/cfg-campaign-links.js:106 Direct innerhtml assignment

medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in scripts/views/cfg-link-settings.js:155

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

scripts/views/cfg-link-settings.js:155 Direct innerhtml assignment

medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in scripts/views/session-tracker.js:92

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

scripts/views/session-tracker.js:92 Direct innerhtml assignment

medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in scripts/views/sidebar.js:47

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

scripts/views/sidebar.js:47 Direct innerhtml assignment

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

Found 60 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 package.json defines install-time lifecycle scripts

preinstall/install/postinstall/prepare scripts execute during dependency installation. Review them carefully for network calls, obfuscation, shell execution, or credential access.

package.json CI/CD securitySupply chainNpm

low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — scripts/auth/core-auth.js:53