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.

crystalbai88-code/my-website

https://github.com/crystalbai88-code/my-website · scanned 2026-06-17 01:51 UTC (1 month, 1 week ago)

114 raw signals (0 security + 114 graph)

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

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

JSON
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all

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.

Legacy markers 5 findings
What it is: TODO, FIXME, XXX, HACK comments. Often indicate a known-broken path the author meant to fix.
Why it matters: Each marker is an unfinished thought. Production code shouldn't ship with debt that's documented but not tracked.
How AI causes it: AI mirrors the style of the codebase, so existing TODOs propagate into new code.
Fix approach: Convert each into a ticket. Delete the comment when the ticket lands. Use a pre-commit hook to block new TODOs without an issue link.
5 matching findings on this repo
  • low Old/deprecated-named symbol `today_legacy` in civ-lab/contemporary_deep.js:133
  • low Old/deprecated-named symbol `today_legacy` in civ-lab/classical_deep.js:399
  • low Old/deprecated-named symbol `today_legacy` in civ-lab/medieval_deep.js:406
  • low Old/deprecated-named symbol `today_legacy` in civ-lab/global_deep.js:159
  • low Old/deprecated-named symbol `today_legacy` in civ-lab/modern_deep.js:133
View all legacy markers findings →
Commented-out code 9 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/`.
9 matching findings on this repo
  • info Commented-code block (5 lines) in civ-lab/early_civ_explorer_data.js:1
  • info Commented-code block (9 lines) in civ-lab/prehistoric_kb.js:1
  • info Commented-code block (7 lines) in civ-lab/classical_deep.js:1
  • info Commented-code block (7 lines) in civ-lab/medieval_deep.js:1
  • info Commented-code block (8 lines) in civ-lab/early_civ_deep.js:1
  • info Commented-code block (5 lines) in civ-lab/data.js:1636
  • info Commented-code block (5 lines) in civ-lab/early_civ_kb.js:1
  • info Commented-code block (6 lines) in civ-lab/classical_people_deep.js:1
  • info Commented-code block (5 lines) in civ-lab/medieval_people_deep.js:1
View all commented-out code 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/9cef40a2-3244-4ee9-b78e-2170d2a7afff/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/9cef40a2-3244-4ee9-b78e-2170d2a7afff/

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.