jaywcjlove/awesome-mac

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.

3 of your 16 findings came from Repobility's proprietary detections. ✓ Repobility tags below mark them.

Scan timing: clone 2.97s · analysis 2.56s · 1.3 MB · GitHub preflight 406ms

https://github.com/jaywcjlove/awesome-mac · scanned 2026-06-05 05:52 UTC (7 hours, 54 minutes ago) · 10 languages

29 findings (15 legacy + 14 scanner) 95th percentile · Unknown · Scanner says 84 (lower by 9)

File as issue Image v2 schema

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 7 hours, 54 minutes ago · v2 · 22 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`	65.0	0.15	9.75
`security_score`	94.4	0.25	23.60
`testing_score`	70.0	0.20	14.00
`documentation_score`	60.0	0.15	9.00
`practices_score`	75.0	0.15	11.25
`code_quality`	79.0	0.10	7.90
Overall		1.00	75.5

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 0 High 4 Medium 10 Low 5 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Legacy 15 9-layer 7 Crowd 0 Layer: Cicd 4 Software 10 Quality 2 Api 1 Hardware 3 Frontend 1 Security 1

Exclude dismissed / FP Exclude test files

Bug-class explainers. Each card groups findings of the same shape — these are the patterns most likely to ship to prod and reappear in future scans unless you systematically fix the cause, not just the instance.

Fragile runtime 2 findings

What it is: Code that runs but breaks under predictable input — division by zero, missing keys, unbounded loops, off-by-one slicing.

Why it matters: Reaches production undetected because happy-path tests pass. First user with a weird input crashes the request.

How AI causes it: AI loves writing the happy path; doesn't probe edge cases unless explicitly asked.

Fix approach: Add property-based tests. Wrap external inputs with explicit validators. Use the framework's typed deserializer (Pydantic, attrs).

2 matching findings on this repo

low Generated build artifact directory is present at repository root dist:1
low Generated build artifact directory is present at repository root build:1

View all fragile runtime findings →

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/780d0553-b604-49e0-85ef-2344b5fb6c0e/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/780d0553-b604-49e0-85ef-2344b5fb6c0e/

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.