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

Shadojin94/ORSG-PRISME-FullStack

https://github.com/Shadojin94/ORSG-PRISME-FullStack · scanned 2026-06-16 00:08 UTC (2 months, 2 weeks ago)

80 raw signals (0 security + 80 graph)

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

Complete repo analysis

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

JSON
Combined
62.6
/100
Security checks
63
0 findings
System graph
63
100.0% cov · 68 findings
Critical
2
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 2 High 12 Medium 11 Low 35 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 68 Crowd 0 Layer: Software 13 Frontend 7 Hardware 3 Security 7 Cicd 1 Quality 18 Api 19
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 62.6/100 with 100.0% coverage. It contains 611 nodes across 27 cross-layer flows, written primarily in mixed languages. Engine surfaced 80 findings — concentrated in quality (21), api (19), security (16). Risk profile is high: 11 critical, 12 high, 11 medium. Recommended next step: open the quality layer findings first — that's where the highest-impact wins live.

Showing 60 of 68 actionable findings. 80 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 3 occurrences Possible secret in Backend/seed_data.mjs
Detected pattern matching password_literal. Rotate the credential and move to a secret manager.
lines 27, 36, 44
Backend/seed_data.mjs:27, 36, 44 (3 hits)
critical System graph security Secrets conf 1.00 8 occurrences Possible secret in Backend/setup_pocketbase.js
Detected pattern matching password_literal. Rotate the credential and move to a secret manager.
lines 233, 234, 261, 262, 263, 264, 265, 266
Backend/setup_pocketbase.js:233, 234, 261, 262, 263, 264, 265, 266 (8 hits)
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/auth/check-email (Frontend/src/hooks/useAuth.ts:70)
`Frontend/src/hooks/useAuth.ts:70` calls `POST /api/auth/check-email` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/auth/check-email` If this points at an external API, prefix it with `https://` so the matcher skip…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/auth/create-user (Frontend/src/pages/AdminUsersPage.tsx:582)
`Frontend/src/pages/AdminUsersPage.tsx:582` calls `POST /api/auth/create-user` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/auth/create-user` If this points at an external API, prefix it with `https://` so the mat…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/auth/forgot-password (Frontend/src/hooks/useAuth.ts:146)
`Frontend/src/hooks/useAuth.ts:146` calls `POST /api/auth/forgot-password` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/auth/forgot-password` If this points at an external API, prefix it with `https://` so the mat…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/auth/forgot-password (Frontend/src/pages/AdminUsersPage.tsx:82)
`Frontend/src/pages/AdminUsersPage.tsx:82` calls `POST /api/auth/forgot-password` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/auth/forgot-password` If this points at an external API, prefix it with `https://` so …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/auth/login-password (Frontend/src/hooks/useAuth.ts:126)
`Frontend/src/hooks/useAuth.ts:126` calls `POST /api/auth/login-password` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/auth/login-password` If this points at an external API, prefix it with `https://` so the match…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/auth/send-code (Frontend/src/hooks/useAuth.ts:87)
`Frontend/src/hooks/useAuth.ts:87` calls `POST /api/auth/send-code` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/auth/send-code` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/auth/set-password (Frontend/src/pages/ProfilePage.tsx:112)
`Frontend/src/pages/ProfilePage.tsx:112` calls `POST /api/auth/set-password` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/auth/set-password` If this points at an external API, prefix it with `https://` so the matc…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/auth/verify-code (Frontend/src/hooks/useAuth.ts:104)
`Frontend/src/hooks/useAuth.ts:104` calls `POST /api/auth/verify-code` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/auth/verify-code` If this points at an external API, prefix it with `https://` so the matcher ski…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/upload (Frontend/src/components/UploadCSV.tsx:49)
`Frontend/src/components/UploadCSV.tsx:49` calls `POST /api/upload` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/upload` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://api.resend.com/emails (Backend/file_server.js:172)
`Backend/file_server.js:172` calls `POST https://api.resend.com/emails` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.resend.com/emails` If this points at an external API, prefix it with `https://` so th…
Dangling fetchFetch
high System graph security auth conf 1.00 FastAPI POST `generate_opendata` without auth dependency — app.py:100
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
app.py:100 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `generate_report` without auth dependency — app.py:65
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
app.py:65 securityAuth fastapi unauth mutation
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — Frontend/src/services/api.ts:37
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 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 hardware Security conf 1.00 Dockerfile runs as root: Dockerfile
No non-root USER set. Containers running as root expand the blast radius of any vulnerability inside the image.
Container
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in app.py:56
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
app.py:56 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in Backend/file_server.js:323
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
Backend/file_server.js:323 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in Backend/file_server.js:10
Found a known-risky pattern (node_child_process). Review and replace if possible.
Backend/file_server.js:10 Node child process
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — Backend/generate_mocao_consolidated.py:83
`subprocess.run(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — Backend/generate_reports.py:426
`requests.get(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.
runtime safetyRobustness
medium System graph cicd CI/CD security conf 1.00 No CI/CD pipelines detected
No GitHub Actions, GitLab CI, or CircleCI configs found. Without CI you can't gate deploys on tests/lints.
CI/CD securityCoverage
medium System graph quality Placeholder conf 1.00 Placeholder or mock-heavy implementation detected
Found 29 placeholder/mock markers across 9 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
2 test file(s) for 76 source file(s) (ratio 0.03). 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 — Frontend/src/components/layout/Sidebar.tsx:93
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 Integrity conf 1.00 6 env vars used in code but missing from .env.example
Drift between code and config docs. The first few: `DEV`, `PORT`, `PRISME_STATE_DIR`, `PYTHON_EXE`, `RESEND_API_KEY`, `VITE_PB_URL`. Add them (with a placeholder/comment) to .env.example so onboarding doesn't break.
config drift
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 545 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 Docker base image is tag-pinned but not digest-pinned: node:20-slim
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
Dockerfile:3 containersPinned dependencies
low System graph quality Integrity conf 1.00 4 occurrences Near-duplicate function bodies in 2 places
Functions with the same first-5-line body hash: app.py:get_available_years_opendata, app.py:get_available_years This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — see https://jw.hn/ai-code-hygiene). Consolidate or document why they're separate.
4 occurrences
repo-level (4 hits)
duplicatesduplication
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `merge_with_old` in Backend/scripts/extract_noyades_pdf.py:261
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 software Dead code conf 1.00 Possibly dead Python function: calc_alloc
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
Backend/generate_opendata_all.py:351
low System graph software Dead code conf 1.00 Possibly dead Python function: calc_familles_mono
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
Backend/generate_opendata_all.py:251
low System graph software Dead code conf 1.00 Possibly dead Python function: calc_pers_menages
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
Backend/generate_opendata_all.py:307
low System graph software Dead code conf 1.00 Possibly dead Python function: calc_pers_sup65ans_seules
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
Backend/generate_opendata_all.py:232
low System graph software Dead code conf 1.00 Possibly dead Python function: calc_pop_inf3ans
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
Backend/generate_opendata_all.py:276
low System graph software Dead code conf 1.00 Possibly dead Python function: calc_types_menages
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
Backend/generate_opendata_all.py:328
low System graph software Dead code conf 1.00 Possibly dead Python function: check_dataset_csv_availability
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
Backend/prisme_engine.py:1302
low System graph software Dead code conf 1.00 Possibly dead Python function: is_guyane_commune
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
Backend/download_opendata.py:423
low System graph software Dead code conf 1.00 Possibly dead Python function: norm_dep
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
Backend/generate_from_opendata.py:961
low System graph software Dead code conf 1.00 Possibly dead Python function: normalize_geo_code
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
Backend/csv_reader.py:198
low System graph software Dead code conf 1.00 Possibly dead Python function: parse_moca_legacy_csv
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
Backend/prisme_engine.py:255
low System graph software Dead code conf 1.00 Possibly dead Python function: reload_config
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
Backend/prisme_engine.py:167
low System graph software Dead code conf 1.00 Possibly dead Python function: sort_key
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
Backend/scripts/extract_noyades_2025_pdf.py:112
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 — Backend/file_server.js:72
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 — Backend/setup_pocketbase.js:56
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: GET /api/available-years
`app.py` declares `GET /api/available-years` 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 /api/available-years-opendata
`app.py` declares `GET /api/available-years-opendata` 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 /api/download/{filename}
`app.py` declares `GET /api/download/{filename}` 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 /api/files
`app.py` declares `GET /api/files` 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 /api/health
`app.py` declares `GET /api/health` 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 /api/themes
`app.py` declares `GET /api/themes` 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 /{catchall:path}
`app.py` declares `GET /{catchall:path}` 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 /api/generate
`app.py` declares `POST /api/generate` 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 /api/generate-opendata
`app.py` declares `POST /api/generate-opendata` 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: Backend/file_server.js (1929 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: Backend/generate_from_opendata.py (1677 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: Backend/prisme_engine.py (1375 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/f090515e-6139-4e5d-b131-65328c19af1d/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/f090515e-6139-4e5d-b131-65328c19af1d/

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.