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

steeven-js/pnm-app

https://github.com/steeven-js/pnm-app · scanned 2026-06-16 00:21 UTC (2 months, 2 weeks ago)

73 raw signals (0 security + 73 graph)

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

Complete repo analysis

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

JSON
Combined
56.2
/100
Security checks
56
0 findings
System graph
56
88.9% cov · 67 findings
Critical
9
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 9 High 11 Medium 26 Low 18 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 67 Crowd 0 Layer: Frontend 4 Network 1 Security 24 Cicd 1 Quality 20 Api 17
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 56.2/100 with 88.9% coverage. It contains 1815 nodes across 6 cross-layer flows, written primarily in mixed languages. Engine surfaced 73 findings — concentrated in security (30), quality (20), api (17). Risk profile is high: 15 critical, 11 high, 26 medium. Recommended next step: open the security layer findings first — that's where the highest-impact wins live.

Showing 64 of 67 actionable findings. 73 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 Possible secret in docs/scripts/Pnm-Restitutions-Entrantes-Bascule.sh
Detected pattern matching password_literal. Rotate the credential and move to a secret manager.
docs/scripts/Pnm-Restitutions-Entrantes-Bascule.sh:54
critical System graph security Secrets conf 1.00 Possible secret in docs/scripts/Pnm-Restitutions-Sortantes-Bascule.sh
Detected pattern matching password_literal. Rotate the credential and move to a secret manager.
docs/scripts/Pnm-Restitutions-Sortantes-Bascule.sh:47
critical System graph security Secrets conf 1.00 Possible secret in docs/scripts/Pnm-Restitutions-Sortantes-Tickets-ratp.sh
Detected pattern matching password_literal. Rotate the credential and move to a secret manager.
docs/scripts/Pnm-Restitutions-Sortantes-Tickets-ratp.sh:42
critical System graph security Secrets conf 1.00 Possible secret in docs/scripts/Pnm-Restitutions-Sortantes-Tickets.sh
Detected pattern matching password_literal. Rotate the credential and move to a secret manager.
docs/scripts/Pnm-Restitutions-Sortantes-Tickets.sh:42
critical System graph security Secrets conf 1.00 Possible secret in docs/scripts/Pnm-Verif-Bascule-MOBI.sh
Detected pattern matching password_literal. Rotate the credential and move to a secret manager.
docs/scripts/Pnm-Verif-Bascule-MOBI.sh:40
critical System graph security Secrets conf 1.00 Possible secret in docs/scripts/Pnm-Verif-Bascule-MOBI_CCA.sh
Detected pattern matching password_literal. Rotate the credential and move to a secret manager.
docs/scripts/Pnm-Verif-Bascule-MOBI_CCA.sh:32
critical System graph security Secrets conf 1.00 Possible secret in resources/js/auth/view/jwt/jwt-sign-in-view.tsx
Detected pattern matching password_literal. Rotate the credential and move to a secret manager.
resources/js/auth/view/jwt/jwt-sign-in-view.tsx:51
critical System graph security Secrets conf 1.00 Possible secret in resources/js/auth/view/jwt/jwt-sign-up-view.tsx
Detected pattern matching password_literal. Rotate the credential and move to a secret manager.
resources/js/auth/view/jwt/jwt-sign-up-view.tsx:56
critical System graph security Secrets conf 1.00 7 occurrences Possible secret in resources/js/routes/paths.ts
Detected pattern matching password_literal. Rotate the credential and move to a secret manager.
lines 16, 17, 26, 32, 33, 42, 43
resources/js/routes/paths.ts:16, 17, 26, 32, 33, 42, 43 (7 hits)
high System graph api Wiring conf 1.00 Dangling fetch: DELETE /api/chat/conversations/${id} (resources/js/components/chat-panel.tsx:113)
`resources/js/components/chat-panel.tsx:113` calls `DELETE /api/chat/conversations/${id}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/chat/conversations/<p>` If this points at an external API, prefix it with `htt…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/chat/conversations (resources/js/components/chat-panel.tsx:77)
`resources/js/components/chat-panel.tsx:77` calls `GET /api/chat/conversations` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/chat/conversations` If this points at an external API, prefix it with `https://` so the …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/chat/conversations/${conv.id} (resources/js/components/chat-panel.tsx:92)
`resources/js/components/chat-panel.tsx:92` calls `GET /api/chat/conversations/${conv.id}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/chat/conversations/<p>` If this points at an external API, prefix it with `ht…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/monitoring/report?date=${date} (resources/js/Pages/Dashboard/components/monitoring/daily-report.tsx:257)
`resources/js/Pages/Dashboard/components/monitoring/daily-report.tsx:257` calls `GET /api/monitoring/report?date=${date}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/monitoring/report` If this points at an extern…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/monitoring?date=${date} (resources/js/Pages/Dashboard/components/monitoring/monitoring-history-drawer.tsx:39)
`resources/js/Pages/Dashboard/components/monitoring/monitoring-history-drawer.tsx:39` calls `GET /api/monitoring?date=${date}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/monitoring` If this points at an external…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/monitoring?date=${date} (resources/js/Pages/Dashboard/components/monitoring/monitoring-timeline.tsx:76)
`resources/js/Pages/Dashboard/components/monitoring/monitoring-timeline.tsx:76` calls `GET /api/monitoring?date=${date}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/monitoring` If this points at an external API, …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/chat/stream (resources/js/hooks/use-chat-stream.ts:39)
`resources/js/hooks/use-chat-stream.ts:39` calls `POST /api/chat/stream` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/chat/stream` If this points at an external API, prefix it with `https://` so the matcher skips …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/monitoring (resources/js/Pages/Dashboard/components/monitoring/monitoring-timeline.tsx:123)
`resources/js/Pages/Dashboard/components/monitoring/monitoring-timeline.tsx:123` calls `POST /api/monitoring` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/monitoring` If this points at an external API, prefix it w…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/sql-playground (resources/js/Pages/Knowledge/components/sql-try-it.tsx:40)
`resources/js/Pages/Knowledge/components/sql-try-it.tsx:40` calls `POST /api/sql-playground` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: axios Normalized path used for matching: `/sql-playground` If this points at an external API, prefix it with `https://…
Dangling fetchAxios
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/sql-playground (resources/js/Pages/SqlPlayground.tsx:105)
`resources/js/Pages/SqlPlayground.tsx:105` calls `POST /api/sql-playground` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: axios Normalized path used for matching: `/sql-playground` If this points at an external API, prefix it with `https://` so the matcher …
Dangling fetchAxios
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/sql-playground (resources/js/Pages/SqlScenarios.tsx:104)
`resources/js/Pages/SqlScenarios.tsx:104` calls `POST /api/sql-playground` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: axios Normalized path used for matching: `/sql-playground` If this points at an external API, prefix it with `https://` so the matcher s…
Dangling fetchAxios
medium System graph frontend Frontend quality conf 1.00 `dangerouslySetInnerHTML` used in a React component — resources/js/layouts/components/notifications-drawer/notification-item.tsx:32
Open XSS surface unless the input is provably trusted. Replace with explicit JSX or sanitize via a vetted library. Why: OWASP basics. Already partially flagged by the security analyzer. Rule id: fq.dangerous-html
Fq dangerous html
medium System graph frontend Frontend quality conf 1.00 `dangerouslySetInnerHTML` used in a React component — resources/js/Pages/CasPratiques.tsx:97
Open XSS surface unless the input is provably trusted. Replace with explicit JSX or sanitize via a vetted library. Why: OWASP basics. Already partially flagged by the security analyzer. Rule id: fq.dangerous-html
Fq dangerous html
medium System graph frontend Frontend quality conf 1.00 `dangerouslySetInnerHTML` used in a React component — resources/js/Pages/Knowledge/components/article-content.tsx:159
Open XSS surface unless the input is provably trusted. Replace with explicit JSX or sanitize via a vetted library. Why: OWASP basics. Already partially flagged by the security analyzer. Rule id: fq.dangerous-html
Fq dangerous html
medium System graph frontend Frontend quality conf 1.00 `dangerouslySetInnerHTML` used in a React component — resources/js/Pages/MobiCasPratiques.tsx:81
Open XSS surface unless the input is provably trusted. Replace with explicit JSX or sanitize via a vetted library. Why: OWASP basics. Already partially flagged by the security analyzer. Rule id: fq.dangerous-html
Fq dangerous html
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, ci, tests, operator-readme. 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 Production readiness conf 1.00 Composite production-readiness gap
Multiple low-cost hardening controls are missing together: license, ci, tests, operator-readme. Opus verification showed these co-occurring gaps are a better readiness signal than reading each flag in isolation.
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 security security conf 1.00 Insecure pattern 'dangerous_innerhtml' in resources/js/layouts/components/notifications-drawer/notification-item.tsx:32
Found a known-risky pattern (dangerous_innerhtml). Review and replace if possible.
resources/js/layouts/components/notifications-drawer/notification-item.tsx:32 Dangerous innerhtml
medium System graph security security conf 1.00 Insecure pattern 'dangerous_innerhtml' in resources/js/Pages/CasPratiques.tsx:97
Found a known-risky pattern (dangerous_innerhtml). Review and replace if possible.
resources/js/Pages/CasPratiques.tsx:97 Dangerous innerhtml
medium System graph security security conf 1.00 Insecure pattern 'dangerous_innerhtml' in resources/js/Pages/Knowledge/components/article-content.tsx:159
Found a known-risky pattern (dangerous_innerhtml). Review and replace if possible.
resources/js/Pages/Knowledge/components/article-content.tsx:159 Dangerous innerhtml
medium System graph security security conf 1.00 Insecure pattern 'dangerous_innerhtml' in resources/js/Pages/MobiCasPratiques.tsx:81
Found a known-risky pattern (dangerous_innerhtml). Review and replace if possible.
resources/js/Pages/MobiCasPratiques.tsx:81 Dangerous innerhtml
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in resources/js/hooks/use-mermaid.ts:36
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
resources/js/hooks/use-mermaid.ts:36 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in resources/js/Pages/Diagrams/Index.tsx:139
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
resources/js/Pages/Diagrams/Index.tsx:139 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in resources/js/Pages/Knowledge/components/article-content.tsx:34
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
resources/js/Pages/Knowledge/components/article-content.tsx:34 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'weak_hash' in resources/js/lib/pnm-code-dictionary.ts:148
Found a known-risky pattern (weak_hash). Review and replace if possible.
resources/js/lib/pnm-code-dictionary.ts:148 Weak hash
medium System graph security security conf 1.00 Insecure pattern 'weak_hash' in resources/js/Pages/CasPratiques.tsx:402
Found a known-risky pattern (weak_hash). Review and replace if possible.
resources/js/Pages/CasPratiques.tsx:402 Weak hash
medium System graph security security conf 1.00 Insecure pattern 'weak_hash' in resources/js/Pages/CasPratiquesPdf.tsx:327
Found a known-risky pattern (weak_hash). Review and replace if possible.
resources/js/Pages/CasPratiquesPdf.tsx:327 Weak hash
medium System graph security security conf 1.00 Insecure pattern 'weak_hash' in resources/js/Pages/Changelog.tsx:156
Found a known-risky pattern (weak_hash). Review and replace if possible.
resources/js/Pages/Changelog.tsx:156 Weak hash
medium System graph security security conf 1.00 Insecure pattern 'weak_hash' in resources/js/Pages/Resolve/Incidents.tsx:911
Found a known-risky pattern (weak_hash). Review and replace if possible.
resources/js/Pages/Resolve/Incidents.tsx:911 Weak hash
medium System graph security security conf 1.00 Insecure pattern 'weak_hash' in resources/js/Pages/Verify/FilenameDecoder.tsx:730
Found a known-risky pattern (weak_hash). Review and replace if possible.
resources/js/Pages/Verify/FilenameDecoder.tsx:730 Weak hash
medium System graph security security conf 1.00 Insecure pattern 'weak_hash' in resources/js/Pages/Verify/Index.tsx:39
Found a known-risky pattern (weak_hash). Review and replace if possible.
resources/js/Pages/Verify/Index.tsx:39 Weak hash
medium System graph security security conf 1.00 Insecure pattern 'weak_hash' in resources/js/Pages/Verify/PortageId.tsx:57
Found a known-risky pattern (weak_hash). Review and replace if possible.
resources/js/Pages/Verify/PortageId.tsx:57 Weak hash
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 69 placeholder/mock markers across 32 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 network Security conf 1.00 Privileged port 10 in use
Port 10 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.
docs/scripts/Pnm-Restitutions-Sortantes-Tickets-ratp.sh Ports
medium System graph quality Tests conf 1.00 Very low test-to-source ratio
0 test file(s) for 412 source file(s) (ratio 0.00). Consider adding integration or unit tests for critical paths.
Coverage
low System graph quality Integrity conf 1.00 Near-duplicate function bodies in 2 places
Functions with the same first-5-line body hash: docs/scripts/md2word.py:main, docs/scripts/md2onenote.py:main 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.
duplicatesduplication
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 Docs conf 1.00 README lacks setup or run instructions
A README exists, but it does not contain common install/setup/run markers. This matches a frequent generated-code pattern: UI is present, operational handoff is thin.
ReadmeRepo hardeningGenerated repo pattern
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 api Wiring conf 1.00 Unused endpoint: DELETE /profile
`resources/js/Pages/Profile/Edit.tsx` declares `DELETE /profile` 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 /glossary
`resources/js/Pages/Glossary/Index.tsx` declares `GET /glossary` 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 /resolve/codes
`resources/js/Pages/Resolve/Codes/Index.tsx` declares `GET /resolve/codes` 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 /profile
`resources/js/Pages/Profile/Edit.tsx` declares `PATCH /profile` 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 /logout
`resources/js/layouts/components/sign-out-button.tsx` declares `POST /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: PUT /password
`resources/js/Pages/Profile/Edit.tsx` declares `PUT /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: resources/js/lib/pnm-utils.ts (2328 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: resources/js/Pages/CasPratiques.tsx (4042 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: resources/js/Pages/CasPratiquesPdf.tsx (3115 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: resources/js/Pages/MobiCrm.tsx (1973 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: resources/js/Pages/OperationsGuide.tsx (1894 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: resources/js/Pages/RequetesPnm.tsx (1316 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: resources/js/Pages/Resolve/Incidents.tsx (1202 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: resources/js/Pages/TicketsKnowledge.tsx (1195 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/2eb7eb2b-bc5a-43b3-81a4-093602792004/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/2eb7eb2b-bc5a-43b3-81a4-093602792004/

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.