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

Scan timing: clone 1.65s · analysis 11.79s · 0.6 MB · GitHub preflight 459ms

Fail2BanEntreprise

https://github.com/Maher-Amara/Fail2BanEntreprise · scanned 2026-06-04 04:06 UTC (1 day, 12 hours ago) · 10 languages

131 findings (71 legacy + 60 scanner) 0th percentile · Typescript · small (2-20K LoC) Scanner says 93 (lower by 63)

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

Complete repo analysis

Last scanned 1 day, 12 hours ago · v3 · 91 findings from 2 sources. Findings combine the legacy security pipeline AND the multi-layer engine (atlas, wiring, flows, ranked) AND verified AI agent contributions.

JSON
Combined
60.8
/100
Repobility
29
71 legacy
9-layer
93
100.0% cov · 20 gaps
Critical
5
click to filter
Agents
6
0 votes
Crowd
0
reported
Score breakdown â 2026-05-18-v5
Component Sub-score Weight Contribution
structure_score 55.0 0.15 8.25
security_score 0.8 0.25 0.20
testing_score 0.0 0.20 0.00
documentation_score 41.0 0.15 6.15
practices_score 50.0 0.15 7.50
code_quality 78.4 0.10 7.84
Overall 1.00 29.9
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all
Severity: Critical 5 High 42 Medium 22 Low 12 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Legacy 71 9-layer 20 Crowd 0 Layer: Software 28 Quality 31 Security 20 Cicd 6 Api 1 Frontend 2 Hardware 3

Top 10 actions, ranked by impact × ease. Severity drives impact; tag-based fix-clarity drives ease.

#1
No CI/CD pipelines detected
GapSeverity.MEDIUM Layer.CICD score 0.225
Why: medium severity
#2
Very low test-to-source ratio
GapSeverity.MEDIUM Layer.QUALITY score 0.225
Why: medium severity
#3
Network/subprocess call without timeout or try/except — agent/agent.py:180
GapSeverity.MEDIUM Layer.QUALITY score 0.225
Why: medium severity · crashes are likely without this
Fix: Add a `timeout=N` argument and wrap in `try/except` in agent/agent.py:180 to prevent hung calls.
#4
`fetch()` without try/.catch or AbortSignal — web/app/page.tsx:187
GapSeverity.MEDIUM Layer.QUALITY score 0.225
Why: medium severity · crashes are likely without this
Fix: Wrap the `fetch(...)` in `try { ... } catch` in web/app/page.tsx:187, OR pass `{ signal: AbortSignal.timeout(N) }` so the call cancels deterministically.
#5
`fetch()` without try/.catch or AbortSignal — web/app/users/page.tsx:18
GapSeverity.MEDIUM Layer.QUALITY score 0.225
Why: medium severity · crashes are likely without this
Fix: Wrap the `fetch(...)` in `try { ... } catch` in web/app/users/page.tsx:18, OR pass `{ signal: AbortSignal.timeout(N) }` so the call cancels deterministically.
#6
`fetch()` without try/.catch or AbortSignal — web/app/invite/[token]/page.tsx:18
GapSeverity.MEDIUM Layer.QUALITY score 0.225
Why: medium severity · crashes are likely without this
Fix: Wrap the `fetch(...)` in `try { ... } catch` in web/app/invite/[token]/page.tsx:18, OR pass `{ signal: AbortSignal.timeout(N) }` so the call cancels deterministically.
#7
`fetch()` without try/.catch or AbortSignal — web/app/components/NavHeader.tsx:21
GapSeverity.MEDIUM Layer.QUALITY score 0.225
Why: medium severity · crashes are likely without this
Fix: Wrap the `fetch(...)` in `try { ... } catch` in web/app/components/NavHeader.tsx:21, OR pass `{ signal: AbortSignal.timeout(N) }` so the call cancels deterministically.
#8
`fetch()` without try/.catch or AbortSignal — web/app/servers/page.tsx:26
GapSeverity.MEDIUM Layer.QUALITY score 0.225
Why: medium severity · crashes are likely without this
Fix: Wrap the `fetch(...)` in `try { ... } catch` in web/app/servers/page.tsx:26, OR pass `{ signal: AbortSignal.timeout(N) }` so the call cancels deterministically.
#9
Stray `console.log` in TS/JS — web/lib/startup.ts:26
GapSeverity.LOW Layer.FRONTEND score 0.170
Why: low severity · fix is short / mechanical
Fix: Delete or guard the `console.log` in web/lib/startup.ts:26.
#10
Docker base image is tag-pinned but not digest-pinned: node:trixie
GapSeverity.LOW Layer.HARDWARE score 0.100
Why: low severity
web/Dockerfile:1

Click "Find this gap" on any action above to jump to it on the Findings tab. Adjust the chip bar to filter by impact (severity), layer, or source.

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/22571c91-55ad-4884-818b-d252be90b564/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/22571c91-55ad-4884-818b-d252be90b564/

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.