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.

linkedin/Liger-Kernel

https://github.com/linkedin/Liger-Kernel · scanned 2026-05-15 18:26 UTC (2 weeks, 6 days ago) · 10 languages

267 findings (124 legacy + 143 scanner) 80th percentile · Python · medium (20-100K LoC) Scanner says 89 (lower by 10)

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 2 weeks, 6 days ago · v1 · 117 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
Score breakdown â 2026-05-14-v3
Component Sub-score Weight Contribution
structure_score 85.0 0.15 12.75
security_score 86.0 0.25 21.50
testing_score 100.0 0.20 20.00
documentation_score 66.0 0.15 9.90
practices_score 65.0 0.15 9.75
code_quality 50.0 0.10 5.00
Overall 1.00 78.9
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all

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

No actionable gaps — clean repo.

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/fedca033-f0ab-4858-8e75-ec394950c9b6/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/fedca033-f0ab-4858-8e75-ec394950c9b6/

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.