up-for-grabs/up-for-grabs.net

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.

24 of your 55 findings came from Repobility's proprietary detections. ✓ Repobility tags below mark them.

Scan timing: clone 4.32s · analysis 23.02s · 3.3 MB · GitHub preflight 502ms

https://github.com/up-for-grabs/up-for-grabs.net · scanned 2026-06-05 13:16 UTC (5 days, 9 hours ago) · 10 languages

217 raw signals (55 security + 162 graph) 87th percentile · Javascript · small (2-20K LoC) System graph score 63 (higher by 24)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

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

JSON

100.0% cov · 71 findings

Score breakdown â 2026-05-18-v5

Component	Sub-score	Weight	Contribution
`structure_score`	100.0	0.15	15.00
`security_score`	79.5	0.25	19.88
`testing_score`	100.0	0.20	20.00
`documentation_score`	61.7	0.15	9.26
`practices_score`	97.0	0.15	14.55
`code_quality`	80.0	0.10	8.00
Overall		1.00	86.7

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 0 High 13 Medium 58 Low 29 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 34 System graph 71 Crowd 0 Layer: Quality 14 Software 26 Cicd 9 Security 1 Frontend 2 Network 47 Hardware 3 Api 3

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.

Config drift 2 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.

2 matching findings on this repo

low File has no detected symbols: vitest.config.ts
low File has no detected symbols: src/content.config.ts

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/8aabf824-9984-4d91-9ee4-8ded66a138c7/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/8aabf824-9984-4d91-9ee4-8ded66a138c7/

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.