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 1.47s · analysis 0.11s · GitHub preflight 509ms

lrrok/are-you-ok

https://github.com/lrrok/are-you-ok.git · scanned 2026-05-26 22:41 UTC (1 week, 2 days ago) · 10 languages

26 findings (12 legacy + 14 scanner) 5th percentile · Javascript · tiny (<2K LoC) Scanner says 89 (lower by 46)

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

Complete repo analysis

Last scanned 1 week, 2 days ago · v2 · 19 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
72.8
/100
Repobility
57
12 legacy
9-layer
89
66.7% cov · 7 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 30.0 0.15 4.50
security_score 97.0 0.25 24.25
testing_score 0.0 0.20 0.00
documentation_score 9.0 0.15 1.35
practices_score 30.0 0.15 4.50
code_quality 80.0 0.10 8.00
Overall 1.00 42.6
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all
Severity: Critical 0 High 1 Medium 8 Low 6 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Legacy 12 9-layer 7 Crowd 0 Layer: Quality 13 Software 2 Api 1 Frontend 1 Security 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 8 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).
8 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
  • medium [ERR002] Empty Catch Block: Empty catch blocks hide errors. app.js:215
  • low Public web app has no humans.txt humans.txt
  • low Public web app has no sitemap sitemap.xml
  • low Public web app has no robots.txt robots.txt
  • high [MINED027] React State Array Mutation: state.X.push/splice/sort followed by set… app.js:163
  • medium `fetch()` without try/.catch or AbortSignal — sw.js:6
View all fragile runtime findings →
Config drift 1 finding
What it is: Settings duplicated across env files, Docker compose, K8s, and code defaults, all with slightly different values.
Why it matters: Production behaviour depends on whichever copy your loader reads first. Subtle bugs in staging that don't reproduce in dev.
How AI causes it: AI writes new config from memory rather than reading the existing source.
Fix approach: Pick one source of truth (env vars + a settings module). Have every other place import from there. Lint for duplicates in CI.
1 matching finding on this repo
  • medium No CI/CD configuration found
View all config drift 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/0cbd5404-c9ad-4b41-94f4-59a5cb0e9c40/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/0cbd5404-c9ad-4b41-94f4-59a5cb0e9c40/

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.