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.

somejohnbforya/whitepoint

https://github.com/somejohnbforya/whitepoint · scanned 2026-06-16 00:17 UTC (2 months, 2 weeks ago)

83 raw signals (0 security + 83 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 2 months, 2 weeks ago · v1 · 83 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 · 83 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 0 High 1 Medium 7 Low 21 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 83 Crowd 0 Layer: Frontend 19 Security 7 Quality 57

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

Showing 29 of 83 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 security security conf 1.00 Insecure pattern 'new_function_used' in tools/gpu-parity.js:67

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

tools/gpu-parity.js:67 New function used

medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — tools/build-gas-lines.js:72

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 security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in docs/convert.html:175

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

docs/convert.html:175 Direct innerhtml assignment

medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in docs/guide.html:285

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

docs/guide.html:285 Direct innerhtml assignment

medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in docs/index.html:224

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

docs/index.html:224 Direct innerhtml assignment

medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in docs/light.html:347

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

docs/light.html:347 Direct innerhtml assignment

medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in tools/build-sky-oracle.js:10

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

tools/build-sky-oracle.js:10 Node child process

medium System graph security Coverage conf 1.00 No auth library detected

The scanner did not find any standard auth library (JWT, OAuth, NextAuth, Auth0, etc.). The repo has auth/admin/session surface indicators, so auth may live in custom code, in a separate service, or be missing.

auth

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

Found 41 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 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 — docs/neon.js:4