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.

schoolie-nagayama-tech/school-management

https://github.com/schoolie-nagayama-tech/school-management · scanned 2026-06-16 00:04 UTC (2 months, 3 weeks ago)

213 raw signals (0 security + 213 graph)

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 2 months, 3 weeks ago · v1 · 210 actionable findings from 1 signal source. 3 repeated signals grouped for readability. 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 2 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.
2 matching findings on this repo
  • medium Insecure pattern 'direct_innerhtml_assignment' in src/app/students/[studentId]/… src/app/students/[studentId]/progress/LegacyProgr…:390
  • low Very large file: src/app/students/[studentId]/progress/LegacyProgressPage.tsx (…
View all legacy markers findings →
Commented-out code 10 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/`.
10 matching findings on this repo
  • info Commented-code block (5 lines) in src/components/course-progress/CourseProgress…
  • info Commented-code block (6 lines) in src/components/proposals/ProposalEditor.tsx:2…
  • info Commented-code block (5 lines) in src/app/schedule/page.tsx:1590
  • info Commented-code block (7 lines) in src/app/api/webhooks/resend/route.ts:41
  • info Commented-code block (6 lines) in src/app/students/[studentId]/progress/NewProg…
  • info Commented-code block (5 lines) in src/app/courses/progress/mockup/page.tsx:270
  • info Commented-code block (9 lines) in src/lib/teacher-tier.ts:1
  • info Commented-code block (6 lines) in src/lib/api/schedule.ts:778
  • info Commented-code block (5 lines) in src/lib/api/seasonalCourses.ts:752
  • info Commented-code block (5 lines) in src/lib/api/pattern-matching.ts:253
View all commented-out code findings →
Config drift 2 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.
2 matching findings on this repo
  • medium Runtime service client appears to use placeholder configuration
  • high Agent instruction/config may expose a secret: .claude/settings.local.json .claude/settings.local.json:86
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/41f34a82-3e10-49b6-b115-246a0d63c65d/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/41f34a82-3e10-49b6-b115-246a0d63c65d/

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.