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.

Scan timing: clone 1.26s · analysis 0.9s · 0.3 MB · GitHub preflight 142ms

ermatteo/FC_nails

https://github.com/ermatteo/FC_nails.git · scanned 2026-05-25 17:01 UTC (1 week, 3 days ago) · 10 languages

152 findings (20 legacy + 132 scanner) 18th percentile · Javascript · small (2-20K LoC) Scanner says 91 (lower by 46)

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 1 week, 3 days ago · v3 · 64 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
Score breakdown â 2026-05-18-v5
Component Sub-score Weight Contribution
structure_score 55.0 0.15 8.25
security_score 100.0 0.25 25.00
testing_score 0.0 0.20 0.00
documentation_score 0.0 0.15 0.00
practices_score 30.0 0.15 4.50
code_quality 75.5 0.10 7.55
Overall 1.00 45.3
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all
9 healthy
page
healthy
page risk 0.40
Home page
healthy
page risk 0.40
Accounting page
healthy
page
auth
Clientdetail page
healthy
page
auth
Clients page
healthy
page
auth
Dashboard page
healthy
page
auth
Inventory page
healthy
page
auth
Statistics page
healthy
page
auth
Treatments page
healthy
page
auth
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/28579a87-a234-43cc-9bfd-e84e1a59f9b8/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/28579a87-a234-43cc-9bfd-e84e1a59f9b8/

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.