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

SamRepository/classement-stages

https://github.com/SamRepository/classement-stages · scanned 2026-06-16 00:01 UTC (2 months, 3 weeks ago)

81 raw signals (0 security + 81 graph)

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

Complete repo analysis

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

JSON
Combined
60.4
/100
Security checks
60
0 findings
System graph
60
100.0% cov · 76 findings
Critical
0
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 0 High 13 Medium 7 Low 53 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 76 Crowd 0 Layer: Software 8 Frontend 2 Hardware 2 Security 17 Cicd 1 Quality 9 Api 37
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 60.4/100 with 100.0% coverage. It contains 578 nodes across 30 cross-layer flows, written primarily in mixed languages. Engine surfaced 81 findings — concentrated in api (37), security (17), quality (14). Risk profile is high: 0 critical, 13 high, 7 medium. Recommended next step: open the api layer findings first — that's where the highest-impact wins live.

Showing 73 of 76 actionable findings. 81 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.

high System graph security auth conf 1.00 FastAPI POST `ajouter_benefice` without auth dependency — webapp/routes/admin.py:132
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
webapp/routes/admin.py:132 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `basculer_actif` without auth dependency — webapp/routes/admin.py:77
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
webapp/routes/admin.py:77 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `creer_utilisateur` without auth dependency — webapp/routes/admin.py:37
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
webapp/routes/admin.py:37 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `decision` without auth dependency — webapp/routes/commission.py:150
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
webapp/routes/commission.py:150 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `geler` without auth dependency — webapp/routes/commission.py:321
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
webapp/routes/commission.py:321 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `importer_utilisateurs` without auth dependency — webapp/routes/admin.py:61
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
webapp/routes/admin.py:61 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `maj_campagne` without auth dependency — webapp/routes/admin.py:185
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
webapp/routes/admin.py:185 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `reinitialiser_motdepasse` without auth dependency — webapp/routes/admin.py:90
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
webapp/routes/admin.py:90 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `reouvrir` without auth dependency — webapp/routes/admin.py:217
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
webapp/routes/admin.py:217 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `supprimer_benefice` without auth dependency — webapp/routes/admin.py:155
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
webapp/routes/admin.py:155 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `tout_valider` without auth dependency — webapp/routes/commission.py:187
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
webapp/routes/commission.py:187 securityAuth fastapi unauth mutation
high System graph security security conf 1.00 Insecure pattern 'eval_used' in classement/engine.py:233
Found a known-risky pattern (eval_used). Review and replace if possible.
classement/engine.py:233 Eval used
high System graph security security conf 1.00 Insecure pattern 'new_function_used' in webapp/static/htmx.min.js:1
Found a known-risky pattern (new_function_used). Review and replace if possible.
webapp/static/htmx.min.js:1 New function used
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: .claude/commands/campagne.md
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/commands/campagne.md 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 ci. 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 security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in webapp/static/htmx.min.js:1
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
webapp/static/htmx.min.js:1 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'domparser_html_parse' in webapp/static/htmx.min.js:1
Found a known-risky pattern (domparser_html_parse). Review and replace if possible.
webapp/static/htmx.min.js:1 Domparser html parse
medium System graph security security conf 1.00 Insecure pattern 'insert_adjacent_html' in webapp/static/htmx.min.js:1
Found a known-risky pattern (insert_adjacent_html). Review and replace if possible.
webapp/static/htmx.min.js:1 Insert adjacent html
medium System graph security Coverage conf 1.00 No auth library detected
The scanner did not find any standard auth library (JWT, OAuth, NextAuth, Auth0, etc.). The repo has auth/admin/session surface indicators, so auth may live in custom code, in a separate service, or be missing.
auth
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
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 48 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: python:3.12-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:2 containersPinned dependencies
low System graph quality Integrity conf 1.00 5 occurrences Near-duplicate function bodies in 2 places
Functions with the same first-5-line body hash: webapp/routes/auth.py:login_form, webapp/routes/auth.py:login 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.
5 occurrences
repo-level (5 hits)
duplicatesduplication
low System graph quality Integrity conf 1.00 2 occurrences Near-duplicate function bodies in 3 places
Functions with the same first-5-line body hash: classement/models.py:to_dict, classement/models.py:to_dict, classement/models.py:to_dict 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.
2 occurrences
repo-level (2 hits)
duplicatesduplication
low System graph quality Integrity conf 1.00 Near-duplicate function bodies in 4 places
Functions with the same first-5-line body hash: webapp/routes/enseignant.py:editer_activite, webapp/routes/enseignant.py:modifier_activite, webapp/routes/enseignant.py:remplace_justificatif, webapp/routes/enseignant.py:supprime_activite This is *the* AI-coder failure mode (4× more duplication in v…
duplicatesduplication
low System graph software Dead code conf 1.00 Possibly dead Python function: checker
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
webapp/auth.py:35
low System graph software Dead code conf 1.00 Possibly dead Python function: current_user
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
webapp/auth.py:19
low System graph software Dead code conf 1.00 Possibly dead Python function: department_label
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
classement/institutions.py:36
low System graph software Dead code conf 1.00 Possibly dead Python function: downgrade
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
webapp/alembic/versions/2c2c05599f46_schema_initial.py:130
low System graph software Dead code conf 1.00 Possibly dead Python function: fmt_da
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
webapp/templating.py:40
low System graph software Dead code conf 1.00 Possibly dead Python function: fmt_points
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
webapp/templating.py:32
low System graph software Dead code conf 1.00 Possibly dead Python function: group_key
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
webapp/services/scoring.py:204
low System graph software Dead code conf 1.00 Possibly dead Python function: upgrade
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
webapp/alembic/versions/2c2c05599f46_schema_initial.py:18
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 — webapp/static/htmx.min.js:1
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 /activites/{entry_id}
`webapp/routes/enseignant.py` declares `DELETE /activites/{entry_id}` 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 /
`webapp/routes/auth.py` declares `GET /` 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 /activites/{entry_id}/edition
`webapp/routes/enseignant.py` declares `GET /activites/{entry_id}/edition` 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 /benefices
`webapp/routes/admin.py` declares `GET /benefices` 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 /budget
`webapp/routes/commission.py` declares `GET /budget` 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 /campagne
`webapp/routes/admin.py` declares `GET /campagne` 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 /classement
`webapp/routes/commission.py` declares `GET /classement` 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 /connexion
`webapp/routes/auth.py` declares `GET /connexion` 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 /dossiers
`webapp/routes/commission.py` declares `GET /dossiers` 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 /dossiers/{dossier_id}
`webapp/routes/commission.py` declares `GET /dossiers/{dossier_id}` 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 /dossiers/{dossier_id}/score
`webapp/routes/commission.py` declares `GET /dossiers/{dossier_id}/score` 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 /exports/{kind}
`webapp/routes/commission.py` declares `GET /exports/{kind}` 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 /justificatifs/{entry_id}
`webapp/routes/fichiers.py` declares `GET /justificatifs/{entry_id}` 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 /mon-mot-de-passe
`webapp/routes/auth.py` declares `GET /mon-mot-de-passe` 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 /sante
`webapp/routes/auth.py` declares `GET /sante` 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 /score
`webapp/routes/enseignant.py` declares `GET /score` 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 /section/{criterion_id}
`webapp/routes/enseignant.py` declares `GET /section/{criterion_id}` 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 /utilisateurs
`webapp/routes/admin.py` declares `GET /utilisateurs` 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 /activites
`webapp/routes/enseignant.py` declares `POST /activites` 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 /activites/{entry_id}/justificatif
`webapp/routes/enseignant.py` declares `POST /activites/{entry_id}/justificatif` 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: POST /activites/{entry_id}/modifier
`webapp/routes/enseignant.py` declares `POST /activites/{entry_id}/modifier` 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 /benefices
`webapp/routes/admin.py` declares `POST /benefices` 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 /benefices/{benefit_id}/supprimer
`webapp/routes/admin.py` declares `POST /benefices/{benefit_id}/supprimer` 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 /campagne
`webapp/routes/admin.py` declares `POST /campagne` 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 /classement/geler
`webapp/routes/commission.py` declares `POST /classement/geler` 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 /connexion
`webapp/routes/auth.py` declares `POST /connexion` 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 /deconnexion
`webapp/routes/auth.py` declares `POST /deconnexion` 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 /dossiers/{dossier_id}/reouvrir
`webapp/routes/admin.py` declares `POST /dossiers/{dossier_id}/reouvrir` 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 /dossiers/{dossier_id}/tout-valider
`webapp/routes/commission.py` declares `POST /dossiers/{dossier_id}/tout-valider` 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: POST /entrees/{criterion_id}
`webapp/routes/enseignant.py` declares `POST /entrees/{criterion_id}` 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 /entrees/{entry_id}/decision
`webapp/routes/commission.py` declares `POST /entrees/{entry_id}/decision` 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 /mon-mot-de-passe
`webapp/routes/auth.py` declares `POST /mon-mot-de-passe` 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 /soumettre
`webapp/routes/enseignant.py` declares `POST /soumettre` 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 /utilisateurs
`webapp/routes/admin.py` declares `POST /utilisateurs` 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 /utilisateurs/import
`webapp/routes/admin.py` declares `POST /utilisateurs/import` 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 /utilisateurs/{user_id}/basculer-actif
`webapp/routes/admin.py` declares `POST /utilisateurs/{user_id}/basculer-actif` 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 /utilisateurs/{user_id}/motdepasse
`webapp/routes/admin.py` declares `POST /utilisateurs/{user_id}/motdepasse` 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
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/fd978c13-e67a-4cc6-b088-a39cac98bb53/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/fd978c13-e67a-4cc6-b088-a39cac98bb53/

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.