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.
Sign up free Scan another repo

Xronuz/Xedu_managment

https://github.com/Xronuz/Xedu_managment · scanned 2026-06-16 01:03 UTC (2 months, 1 week ago)

238 raw signals (0 security + 238 graph)

File as issue Image
UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 2 months, 1 week ago · v1 · 197 actionable findings from 1 signal source. 41 repeated signals grouped for readability. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON
Combined
63.2
/100
Security checks
63
0 findings
System graph
63
100.0% cov · 197 findings
Critical
13
click to filter
Agents
10
0 votes
Crowd
0
reported
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all
Severity: Critical 13 High 0 Medium 7 Low 89 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 197 Crowd 0 Layer: Frontend 98 Hardware 2 Security 14 Quality 33 Api 50
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 63.2/100 with 100.0% coverage. It contains 3902 nodes across 30 cross-layer flows, written primarily in mixed languages. Engine surfaced 238 findings — concentrated in frontend (98), security (52), api (50). Risk profile is high: 51 critical, 0 high, 7 medium. Recommended next step: open the frontend layer findings first — that's where the highest-impact wins live.

Showing 104 of 197 actionable findings. 238 raw detector signals were grouped into reader-sized issues. Click TP / FP to vote on a finding's accuracy — votes adjust the confidence weighting and improve detection across the platform.

critical System graph security Secrets conf 1.00 7 occurrences Possible secret in apps/backend/prisma/seed-demo.ts
Detected pattern matching password_literal. Rotate the credential and move to a secret manager.
lines 183, 184, 185, 186, 187, 188, 189
apps/backend/prisma/seed-demo.ts:183, 184, 185, 186, 187, 188, 189 (7 hits)
critical System graph security Secrets conf 1.00 9 occurrences Possible secret in apps/backend/prisma/seed.ts
Detected pattern matching password_literal. Rotate the credential and move to a secret manager.
lines 86, 95, 104, 113, 122, 131, 140, 149, +1 more
apps/backend/prisma/seed.ts:86, 95, 104, 113, 122, 131, 140, 149, +1 more (9 hits)
critical System graph security Secrets conf 1.00 Possible secret in apps/frontend/src/app/(auth)/accept-invite/page.tsx
Detected pattern matching password_literal. Rotate the credential and move to a secret manager.
apps/frontend/src/app/(auth)/accept-invite/page.tsx:89
critical System graph security Secrets conf 1.00 Possible secret in apps/frontend/src/app/(auth)/first-login/page.tsx
Detected pattern matching password_literal. Rotate the credential and move to a secret manager.
apps/frontend/src/app/(auth)/first-login/page.tsx:84
critical System graph security Secrets conf 1.00 Possible secret in apps/frontend/src/app/(auth)/reset-password/page.tsx
Detected pattern matching password_literal. Rotate the credential and move to a secret manager.
apps/frontend/src/app/(auth)/reset-password/page.tsx:116
critical System graph security Secrets conf 1.00 Possible secret in apps/frontend/src/app/(dashboard)/dashboard/classes/[id]/page.tsx
Detected pattern matching password_literal. Rotate the credential and move to a secret manager.
apps/frontend/src/app/(dashboard)/dashboard/classes/[id]/page.tsx:104
critical System graph security Secrets conf 1.00 3 occurrences Possible secret in apps/frontend/src/app/(dashboard)/dashboard/profile/page.tsx
Detected pattern matching password_literal. Rotate the credential and move to a secret manager.
lines 92, 93, 94
apps/frontend/src/app/(dashboard)/dashboard/profile/page.tsx:92, 93, 94 (3 hits)
critical System graph security Secrets conf 1.00 3 occurrences Possible secret in apps/frontend/src/app/(dashboard)/dashboard/settings/page.tsx
Detected pattern matching password_literal. Rotate the credential and move to a secret manager.
lines 262, 263, 264
apps/frontend/src/app/(dashboard)/dashboard/settings/page.tsx:262, 263, 264 (3 hits)
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — apps/frontend/src/app/(dashboard)/dashboard/_components/shared-widgets.tsx:806
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 quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — apps/frontend/src/app/(dashboard)/dashboard/system-health/page.tsx:124
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 quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: .claude/launch.json
This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.
.claude/launch.json VerificationClaude instruction
medium System graph quality Agent instructions conf 1.00 Agent instructions exist but release-hardening basics are missing
AI-coder instruction files were found, but the repo is missing license, lockfile. Treat this as a contract gap: the agent is guided, but the generated output is not yet guarded by the controls that make it repeatable.
Repo hardeningGenerated repo pattern
medium System graph quality Placeholder conf 1.00 Critical user flow still appears backed by mock or placeholder data
A payment/auth/admin/order/billing-style flow contains mock, fake, TODO, dummy, or placeholder markers in runtime source. In the Fable corpus this is a high-leverage completeness smell: the app can look finished while the money, identity, or tenant flow is still scaffolded.
Mock dataCritical flowGenerated repo pattern
medium System graph quality Placeholder conf 1.00 Placeholder or mock-heavy implementation detected
Found 358 placeholder/mock markers across 84 source files. This often means the repo looks complete while core flows still use generated scaffolding or fake data.
Mock dataIncompleteGenerated repo pattern
medium System graph quality Tests conf 1.00 Very low test-to-source ratio
15 test file(s) for 731 source file(s) (ratio 0.02). Consider adding integration or unit tests for critical paths.
Coverage
low System graph frontend Frontend quality conf 1.00 "active" state uses light bg in a dark theme — apps/frontend/src/app/(dashboard)/dashboard/alerts/page.tsx:504
A ternary like `active ? 'bg-white' : '...'` (or bg-gray-100/200) on a dark theme produces jarring white pills. Use a dark-emphasized active state instead — border + ring or slightly brighter dark bg. Example: `active ? 'bg-gray-800 border-gray-500 ring-1 ring-blue-500/30' : '…'`. Why: P-E in CHEC…
Fq active light bg
low System graph frontend Frontend quality conf 1.00 "active" state uses light bg in a dark theme — apps/frontend/src/app/(dashboard)/dashboard/approvals/page.tsx:383
A ternary like `active ? 'bg-white' : '...'` (or bg-gray-100/200) on a dark theme produces jarring white pills. Use a dark-emphasized active state instead — border + ring or slightly brighter dark bg. Example: `active ? 'bg-gray-800 border-gray-500 ring-1 ring-blue-500/30' : '…'`. Why: P-E in CHEC…
Fq active light bg
low System graph frontend Frontend quality conf 1.00 "active" state uses light bg in a dark theme — apps/frontend/src/app/(dashboard)/dashboard/schedule/_components/schedule-workspace.tsx:317
A ternary like `active ? 'bg-white' : '...'` (or bg-gray-100/200) on a dark theme produces jarring white pills. Use a dark-emphasized active state instead — border + ring or slightly brighter dark bg. Example: `active ? 'bg-gray-800 border-gray-500 ring-1 ring-blue-500/30' : '…'`. Why: P-E in CHEC…
Fq active light bg
low System graph quality Production readiness conf 1.00 Composite production-readiness gap
Multiple low-cost hardening controls are missing together: license, lockfile. Opus verification showed these co-occurring gaps are a better readiness signal than reading each flag in isolation.
Repo hardeningGenerated repo pattern
low System graph hardware Coverage conf 1.00 Containers defined but no K8s/orchestration manifest found
Repo has Dockerfiles/compose but no Kubernetes/Nomad manifests. If the target deployment is K8s, the manifests may live in a separate ops repo.
Deployment
low System graph quality Debug conf 1.00 Debug logging residue appears in source files
Found 175 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 hardware Supply chain conf 1.00 4 occurrences Docker base image is tag-pinned but not digest-pinned: node:20-alpine
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
2 files, 4 locations
apps/backend/Dockerfile:2, 37 (2 hits)
apps/frontend/Dockerfile:2, 43 (2 hits)
containersPinned dependencies
low System graph security security conf 1.00 Insecure pattern 'document_write' in apps/frontend/src/hooks/use-print.ts:96
Found a known-risky pattern (document_write). Review and replace if possible.
apps/frontend/src/hooks/use-print.ts:96 Document write
low System graph quality License conf 1.00 No license file detected
No LICENSE/COPYING/NOTICE file was found. Generated repositories often omit licensing, which blocks reuse and automated intake.
Repo hardeningGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: apps/backend/package.json
`package.json` declares dependencies, but no same-directory npm/pnpm/yarn/bun lockfile was found. Generated projects without lockfiles are less reproducible and harder to secure-scan precisely.
apps/backend/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: apps/frontend/package.json
`package.json` declares dependencies, but no same-directory npm/pnpm/yarn/bun lockfile was found. Generated projects without lockfiles are less reproducible and harder to secure-scan precisely.
apps/frontend/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: packages/types/package.json
`package.json` declares dependencies, but no same-directory npm/pnpm/yarn/bun lockfile was found. Generated projects without lockfiles are less reproducible and harder to secure-scan precisely.
packages/types/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `daysOld` in apps/frontend/src/app/(dashboard)/dashboard/alerts/page.tsx:140
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
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 — apps/backend/prisma/seed-demo.ts:108
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — apps/backend/prisma/seed-risk-test.ts:194
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — apps/backend/prisma/seed-specific-users.ts:12
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — apps/backend/prisma/seed.ts:19
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — apps/backend/scripts/audit-permissions.ts:162
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — apps/backend/scripts/audit-routes.ts:76
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — apps/backend/scripts/backfill-main-campus.ts:15
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — apps/backend/scripts/normalize-emails.ts:30
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — apps/backend/scripts/recover-access.ts:32
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — apps/backend/scripts/validate-demo.ts:55
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — apps/backend/src/modules/schedule/advanced-solver.service.spec.ts:532
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — apps/backend/src/modules/schedule/schedule.service.benchmark.spec.ts:235
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — apps/frontend/src/hooks/use-socket.ts:68
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — scripts/audit-branch-admin-escalation.js:22
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — scripts/cleanup-class-branchid.ts:25
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph api Wiring conf 1.00 Unused endpoint: DELETE /notifications/queue-failed
`apps/frontend/src/app/(dashboard)/dashboard/system-health/page.tsx` declares `DELETE /notifications/queue-failed` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider remo…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /discipline
`apps/frontend/src/lib/api/discipline.ts` declares `GET /discipline` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /discipline/stats
`apps/frontend/src/lib/api/discipline.ts` declares `GET /discipline/stats` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /fee-structures
`apps/frontend/src/lib/api/fee-structures.ts` declares `GET /fee-structures` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /invitations
`apps/frontend/src/lib/api/invitations.ts` declares `GET /invitations` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /leave-requests
`apps/frontend/src/lib/api/leave-requests.ts` declares `GET /leave-requests` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /library/loans
`apps/frontend/src/app/(dashboard)/dashboard/_components/librarian-dashboard.tsx` declares `GET /library/loans` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removin…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /library/stats
`apps/frontend/src/app/(dashboard)/dashboard/_components/librarian-dashboard.tsx` declares `GET /library/stats` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removin…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /notifications
`apps/frontend/src/lib/api/notifications.ts` declares `GET /notifications` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /notifications/preferences
`apps/frontend/src/lib/api/notifications.ts` declares `GET /notifications/preferences` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who cons…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /notifications/queue-stats
`apps/frontend/src/app/(dashboard)/dashboard/system-health/page.tsx` declares `GET /notifications/queue-stats` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /reports/analytics/alerts
`apps/frontend/src/lib/api/analytics.ts` declares `GET /reports/analytics/alerts` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes …
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /reports/analytics/branch-comparison
`apps/frontend/src/lib/api/analytics.ts` declares `GET /reports/analytics/branch-comparison` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting wh…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /reports/analytics/finance
`apps/frontend/src/lib/api/analytics.ts` declares `GET /reports/analytics/finance` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /reports/analytics/marketing-roi
`apps/frontend/src/lib/api/analytics.ts` declares `GET /reports/analytics/marketing-roi` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who co…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /reports/analytics/pulse
`apps/frontend/src/lib/api/analytics.ts` declares `GET /reports/analytics/pulse` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes i…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /reports/export/excel
`apps/frontend/src/lib/api/analytics.ts` declares `GET /reports/export/excel` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /super-admin/stats
`apps/frontend/src/app/(dashboard)/dashboard/system-health/page.tsx` declares `GET /super-admin/stats` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or docu…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /teaching-loads
`apps/frontend/src/lib/api/teaching-load.ts` declares `GET /teaching-loads` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /teaching-loads/workload/summary
`apps/frontend/src/lib/api/teaching-load.ts` declares `GET /teaching-loads/workload/summary` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting wh…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /teaching-loads/workload/teachers
`apps/frontend/src/lib/api/teaching-load.ts` declares `GET /teaching-loads/workload/teachers` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting w…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /users/check-email
`apps/frontend/src/lib/api/users.ts` declares `GET /users/check-email` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: PATCH /notifications/preferences
`apps/frontend/src/lib/api/notifications.ts` declares `PATCH /notifications/preferences` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who co…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /auth/forgot-password
`apps/frontend/src/lib/api/auth.ts` declares `POST /auth/forgot-password` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /auth/logout
`apps/frontend/src/lib/api/auth.ts` declares `POST /auth/logout` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /auth/reset-password
`apps/frontend/src/lib/api/auth.ts` declares `POST /auth/reset-password` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /discipline
`apps/frontend/src/lib/api/discipline.ts` declares `POST /discipline` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /fee-structures
`apps/frontend/src/lib/api/fee-structures.ts` declares `POST /fee-structures` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /import/attendance/commit
`apps/frontend/src/lib/api/import.ts` declares `POST /import/attendance/commit` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /import/attendance/parse
`apps/frontend/src/lib/api/import.ts` declares `POST /import/attendance/parse` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /import/grades/commit
`apps/frontend/src/lib/api/import.ts` declares `POST /import/grades/commit` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /import/grades/parse
`apps/frontend/src/lib/api/import.ts` declares `POST /import/grades/parse` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /import/schedule/commit
`apps/frontend/src/lib/api/import.ts` declares `POST /import/schedule/commit` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /import/schedule/parse
`apps/frontend/src/lib/api/import.ts` declares `POST /import/schedule/parse` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /import/students/commit
`apps/frontend/src/lib/api/import.ts` declares `POST /import/students/commit` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /import/students/parse
`apps/frontend/src/lib/api/import.ts` declares `POST /import/students/parse` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /import/users/commit
`apps/frontend/src/lib/api/import.ts` declares `POST /import/users/commit` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /import/users/parse
`apps/frontend/src/lib/api/import.ts` declares `POST /import/users/parse` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /leave-requests
`apps/frontend/src/lib/api/leave-requests.ts` declares `POST /leave-requests` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /notifications
`apps/frontend/src/lib/api/notifications.ts` declares `POST /notifications` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /notifications/broadcast
`apps/frontend/src/lib/api/notifications.ts` declares `POST /notifications/broadcast` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consu…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /teaching-loads
`apps/frontend/src/lib/api/teaching-load.ts` declares `POST /teaching-loads` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /teaching-loads/import/commit
`apps/frontend/src/lib/api/teaching-load.ts` declares `POST /teaching-loads/import/commit` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who …
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /teaching-loads/import/preview
`apps/frontend/src/lib/api/teaching-load.ts` declares `POST /teaching-loads/import/preview` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /upload/document
`apps/frontend/src/app/(dashboard)/dashboard/homework/page.tsx` declares `POST /upload/document` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documentin…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /users
`apps/frontend/src/lib/api/users.ts` declares `POST /users` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /users/import/csv
`apps/frontend/src/lib/api/users.ts` declares `POST /users/import/csv` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: PUT /notifications/read-all
`apps/frontend/src/lib/api/notifications.ts` declares `PUT /notifications/read-all` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consume…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: PUT /users/me/avatar
`apps/frontend/src/lib/api/users.ts` declares `PUT /users/me/avatar` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: PUT /users/me/password
`apps/frontend/src/lib/api/users.ts` declares `PUT /users/me/password` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph quality Complexity conf 1.00 Very large file: apps/backend/src/modules/payroll/payroll.service.ts (1409 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: apps/frontend/src/app/(dashboard)/dashboard/crm/page.tsx (1670 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: apps/frontend/src/app/(dashboard)/dashboard/exams/[id]/page.tsx (1378 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: apps/frontend/src/app/(dashboard)/dashboard/exams/_components/exams-workspace.tsx (1570 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: apps/frontend/src/app/(dashboard)/dashboard/grades/page.tsx (1219 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: apps/frontend/src/app/(dashboard)/dashboard/parent/page.tsx (1091 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: apps/frontend/src/app/(dashboard)/dashboard/payroll/page.tsx (1747 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: apps/frontend/src/app/(dashboard)/dashboard/reports/_components/reports-workspace.tsx (1300 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: apps/frontend/src/app/(dashboard)/dashboard/schedule/_components/schedule-workspace.tsx (1362 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: apps/frontend/src/app/(dashboard)/dashboard/users/page.tsx (1241 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
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/9c104d47-94a6-457f-af56-5085cc882e49/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/9c104d47-94a6-457f-af56-5085cc882e49/

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.