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

felladrin/MiniSearch

https://github.com/felladrin/MiniSearch · scanned 2026-05-15 17:13 UTC (2 weeks, 6 days ago) · 10 languages

65 findings (20 legacy + 45 scanner) 79th percentile · Typescript · small (2-20K LoC) Scanner says 86 (lower by 4)

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

Complete repo analysis

Last scanned 2 weeks, 6 days ago · v1 · 17 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
84.1
/100
Repobility
82
17 legacy
9-layer
86
100.0% cov · 0 gaps
Critical
0
click to filter
Agents
6
0 votes
Crowd
0
reported
Score breakdown â 2026-05-17-v4 calibration-aware
Component Sub-score Weight Contribution
structure_score 75.0 0.15 11.25
security_score 89.0 0.25 22.25
testing_score 83.0 0.20 16.60
documentation_score 58.7 0.15 8.80
practices_score 100.0 0.15 15.00
code_quality 80.0 0.10 8.00
Overall 1.00 81.9
Calibrated penalty buckets (security_score): web: 3.0 · docker: 6.1 · threat: 2.0
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all
Severity: Critical 0 High 3 Medium 6 Low 7 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Legacy 17 9-layer 0 Crowd 0 Layer: Quality 6 Cicd 10 Security 1

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 6 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).
6 matching findings on this repo
  • medium Public web service has no security.txt .well-known/security.txt
  • medium Public web app has no Content Security Policy index.html
  • low robots.txt does not advertise a sitemap client/public/robots.txt
  • low Public web app has no humans.txt humans.txt
  • low Public docs site has no llms.txt llms.txt
  • low Public web app has no sitemap sitemap.xml
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/06282029-d006-40f6-a20e-26ca80c0d64b/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/06282029-d006-40f6-a20e-26ca80c0d64b/

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.