remsky/Kokoro-FastAPI

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.

https://github.com/remsky/Kokoro-FastAPI · scanned 2026-05-15 03:48 UTC (3 weeks ago) · 10 languages

157 findings (52 legacy + 105 scanner) 56th percentile · Python · small (2-20K LoC) Scanner says 44 (higher by 29)

File as issue Image v2 schema

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 3 weeks ago · v1 · 44 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-17-v4 calibration-aware

Component	Sub-score	Weight	Contribution
`structure_score`	60.0	0.15	9.00
`security_score`	53.5	0.25	13.38
`testing_score`	95.0	0.20	19.00
`documentation_score`	97.0	0.15	14.55
`practices_score`	65.0	0.15	9.75
`code_quality`	74.5	0.10	7.45
Overall		1.00	73.1

Calibrated penalty buckets (security_score): web: 1.6 Â· authz: 5.5 Â· docker: 32.9 Â· threat: 14.5

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 0 High 23 Medium 8 Low 8 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Legacy 44 9-layer 0 Crowd 0 Layer: Quality 9 Security 11 Cicd 23 Software 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 9 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).

9 matching findings on this repo

medium Public web service has no security.txt .well-known/security.txt
medium [ERR002] Empty Catch Block: Empty catch blocks hide errors. web/src/services/AudioService.js:476
medium [ERR001] Silent Exception Swallowing: Silently swallowing all exceptions hides … api/src/routers/debug.py:206
medium [ERR001] Silent Exception Swallowing: Silently swallowing all exceptions hides … api/src/routers/openai_compatible.py:367
medium [ERR001] Silent Exception Swallowing: Silently swallowing all exceptions hides … api/src/routers/development.py:369
medium Duplicated implementation block across source files dev/Test copy 2.py:6
medium Duplicated implementation block across source files api/src/routers/openai_compatible.py:222
medium Parallel implementation file sits beside a canonical file dev/Test copy.py:1
low Source file name looks like an AI patch artifact api/src/inference/kokoro_v1.py: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/379fc10a-3993-4a3f-9a62-1de646e19385/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/379fc10a-3993-4a3f-9a62-1de646e19385/

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.