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

Scan timing: clone 6.7s · analysis 0.15s · 4.0 MB · GitHub API rate-limit (preflight)

nuelporto/studio-assaka

https://github.com/nuelporto/studio-assaka.git · scanned 2026-05-27 06:37 UTC (1 week, 2 days ago) · 10 languages

18 findings (10 legacy + 8 scanner) 70th percentile · Javascript · tiny (<2K LoC) Scanner says 92 (lower by 16)

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

Complete repo analysis

Last scanned 1 week, 2 days ago · v2 · 14 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
Combined
89.5
/100
Repobility
87
10 legacy
9-layer
92
77.8% cov · 4 gaps
Critical
0
click to filter
Agents
6
0 votes
Crowd
0
reported
Score breakdown â 2026-05-18-v5
Component Sub-score Weight Contribution
structure_score 90.0 0.15 13.50
security_score 95.9 0.25 23.98
testing_score 70.0 0.20 14.00
documentation_score 38.7 0.15 5.81
practices_score 72.0 0.15 10.80
code_quality 80.0 0.10 8.00
Overall 1.00 76.1
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all
Severity: Critical 0 High 0 Medium 6 Low 6 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Legacy 10 9-layer 4 Crowd 0 Layer: Quality 9 Security 3 Api 1 Cicd 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 7 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).
7 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 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
  • low Public web app has no robots.txt robots.txt
  • info [MINED056] React Key As Index: key={index} in map() — re-renders the wrong elem… src/app/page.js:126
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/bfc20983-71d4-4a69-8248-729eb092b808/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/bfc20983-71d4-4a69-8248-729eb092b808/

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.