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.

RiverTech-devs/student-portal

https://github.com/RiverTech-devs/student-portal · scanned 2026-06-15 23:52 UTC (2 months, 3 weeks ago)

121 raw signals (0 security + 121 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 2 months, 3 weeks ago · v1 · 121 actionable findings from 1 signal source. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON

100.0% cov · 121 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 2 High 7 Medium 40 Low 48 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 121 Crowd 0 Layer: Api 1 Frontend 36 Security 37 Cicd 1 Quality 46

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.

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

low Old/deprecated-named symbol `loadDomainAsLegacy` in shared/graph-data.js:270
low Old/deprecated-named symbol `migLegacy` in tools/crossref-csv-vs-seed.js:278

View all legacy markers findings →

Commented-out code 21 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 (7 lines) in firebase/firebase-config.js:4
info Commented-code block (6 lines) in shared/config.js:43
info Commented-code block (6 lines) in viewer/3d/app.js:142
info Commented-code block (14 lines) in viewer/3d/data.js:8
info Commented-code block (15 lines) in supabase/functions/pin-login/index.ts:7
info Commented-code block (7 lines) in tools/strip-dead-practice.js:1
info Commented-code block (6 lines) in tools/fix-template-bugs.js:1
info Commented-code block (6 lines) in tools/reconcile-3d-vs-master.js:1
info Commented-code block (6 lines) in tools/rls-audit.js:14
info Commented-code block (10 lines) in tools/fix-subskill-gates.js:6
info Commented-code block (8 lines) in tools/split-subtypes.js:4
info Commented-code block (5 lines) in tools/audit-lessons.js:1

View all commented-out code findings →

Config drift 6 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.

6 matching findings on this repo

low Stray `console.log` in TS/JS — shared/config.js:60
critical Possible secret in firebase/firebase-config.js firebase/firebase-config.js:13
medium Insecure pattern 'direct_innerhtml_assignment' in shared/config.js:136 shared/config.js:136
medium Runtime service client appears to use placeholder configuration
info Commented-code block (7 lines) in firebase/firebase-config.js:4
info Commented-code block (6 lines) in shared/config.js:43

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/b5c72e88-0710-4ec9-b6da-a75a31c0ba61/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/b5c72e88-0710-4ec9-b6da-a75a31c0ba61/

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.