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
54 of your 159 findings came from Repobility's proprietary detections. ✓ Repobility tags below mark them.

Scan timing: clone 4.42s · analysis 64.55s · 11.5 MB · GitHub preflight 420ms

thedaviddias/Front-End-Checklist

https://github.com/thedaviddias/Front-End-Checklist · scanned 2026-06-05 08:06 UTC (5 days, 22 hours ago) · 10 languages

493 raw signals (147 security + 346 graph) 16th percentile · Typescript · medium (20-100K LoC) System graph score 67 (lower by 14)

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

Complete repo analysis

Last scanned 5 days, 22 hours ago · v2 · 173 actionable findings from 2 signal sources. 147 repeated signals grouped for readability. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON
Combined
54.5
/100
Security checks
42
54 findings
System graph
67
100.0% cov · 119 findings
Critical
3
click to filter
Agents
6
0 votes
Crowd
0
reported
Score breakdown â 2026-05-18-v5
Component Sub-score Weight Contribution
structure_score 60.0 0.15 9.00
security_score 11.5 0.25 2.88
testing_score 72.0 0.20 14.40
documentation_score 50.8 0.15 7.62
practices_score 94.0 0.15 14.10
code_quality 58.1 0.10 5.81
Overall 1.00 53.8
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all
Severity: Critical 3 High 18 Medium 25 Low 97 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 54 System graph 119 Crowd 0 Layer: Quality 35 Security 22 Software 64 Cicd 5 Api 1 Frontend 46

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.

Config drift 5 findings
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.
5 matching findings on this repo
  • low File has no detected symbols: commitlint.config.js
  • low File has no detected symbols: apps/web/playwright.config.ts
  • low File has no detected symbols: apps/web/sentry.server.config.ts
  • low File has no detected symbols: apps/web/sentry.edge.config.ts
  • low File has no detected symbols: apps/web/postcss.config.js
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/44e4ee1f-a4a7-44b3-95ef-0df7bb1822af/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/44e4ee1f-a4a7-44b3-95ef-0df7bb1822af/

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.