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.

RuiminYan/cuberoot.me

https://github.com/RuiminYan/cuberoot.me · scanned 2026-06-16 00:00 UTC (2 months, 3 weeks ago)

836 raw signals (2 security + 834 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 2 months, 3 weeks ago · v1 · 833 actionable findings from 2 signal sources. 3 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 · 831 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 0 High 63 Medium 219 Low 274 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 2 System graph 831 Crowd 0 Layer: Quality 493 Frontend 142 Network 5 Security 129 Cicd 2 Api 62

Exclude dismissed / FP Exclude test files

Bug-class explainers. Each card groups findings of the same shape — these are the patterns most likely to ship to prod and reappear in future scans unless you systematically fix the cause, not just the instance.

Commented-out code 255 findings

What it is: Lines of source that were intentionally disabled but never deleted.

Why it matters: Git already remembers history — commented code rots, becomes wrong, and adds noise to diffs.

How AI causes it: AI sometimes comments out broken code instead of fixing it. Reviewers approve out of inertia.

Fix approach: Delete. Trust `git log`. If you really need to remember, save it in a notes file under `docs/`.

12 matching findings on this repo

info Commented-code block (5 lines) in solver/333opt/solve.mjs:3
info Commented-code block (5 lines) in solver/333opt/gen-table.mjs:1
info Commented-code block (5 lines) in solver/333opt/inject.mjs:10
info Commented-code block (5 lines) in tools/i18n/i18n.js:739
info Commented-code block (8 lines) in tools/cstimer-scramble/scrambler.worker.js:26
info Commented-code block (5 lines) in tools/cstimer-scramble/scramble/scramble_sq1_…
info Commented-code block (5 lines) in tools/cstimer-scramble/lib/mathlib.js:1049
info Commented-code block (7 lines) in tools/solver/rust-cross/cross-solver-worker.j…
info Commented-code block (6 lines) in tools/src/filter/filter.js:973
info Commented-code block (13 lines) in core/packages/client/proxy.ts:3
info Commented-code block (6 lines) in core/packages/client/next.config.ts:18
info Commented-code block (6 lines) in core/packages/client/i18n/i18n-client.ts:4

View all commented-out code findings →

Config drift 4 findings

What it is: Settings duplicated across env files, Docker compose, K8s, and code defaults, all with slightly different values.

Why it matters: Production behaviour depends on whichever copy your loader reads first. Subtle bugs in staging that don't reproduce in dev.

How AI causes it: AI writes new config from memory rather than reading the existing source.

Fix approach: Pick one source of truth (env vars + a settings module). Have every other place import from there. Lint for duplicates in CI.

4 matching findings on this repo

info TODO/FIXME marker in shipping code — core/packages/client/lib/roux/Config.ts:153
high Agent instruction/config may expose a secret: .claude/skills/scramble-stats-bui… .claude/skills/scramble-stats-build/SKILL.md:24
info Commented-code block (6 lines) in core/packages/client/next.config.ts:18
info Commented-code block (6 lines) in core/packages/client/lib/roux/Config.ts:98

View all config drift findings →

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/9e8c3bd8-a1c3-48d2-af55-42c35b81bdb9/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/9e8c3bd8-a1c3-48d2-af55-42c35b81bdb9/

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.