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

mihaelamj/cupertino

https://github.com/mihaelamj/cupertino.git · scanned 2026-05-16 02:00 UTC (2 weeks, 6 days ago) · 10 languages

23 findings (14 legacy + 9 scanner) Scanner says 90 (lower by 16)

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

Complete repo analysis

Last scanned 2 weeks, 6 days ago · v1 · 14 findings from 1 source. Findings combine the legacy security pipeline AND the multi-layer engine (atlas, wiring, flows, ranked) AND verified AI agent contributions.

JSON
Combined
80.9
/100
Repobility
72
14 legacy
9-layer
90
77.8% cov · 0 gaps
Critical
0
click to filter
Agents
6
0 votes
Crowd
0
reported
Score breakdown â 2026-05-14-v3
Component Sub-score Weight Contribution
structure_score 40.0 0.15 6.00
security_score 100.0 0.25 25.00
testing_score 80.0 0.20 16.00
documentation_score 85.0 0.15 12.75
practices_score 65.0 0.15 9.75
code_quality 50.0 0.10 5.00
Overall 1.00 74.5
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all
Severity: Critical 0 High 13 Medium 1 Low 0 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Legacy 14 9-layer 0 Crowd 0 Layer: Quality 14
No flows synthesized yet.
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/73d7072b-bd49-4373-a5c3-3b4aa9e3d759/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/73d7072b-bd49-4373-a5c3-3b4aa9e3d759/

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.