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 2.66s · analysis 0.07s · GitHub preflight 406ms

poletseib-ui/Projecte-Vaquer

https://github.com/poletseib-ui/Projecte-Vaquer.git · scanned 2026-05-26 22:31 UTC (2 weeks, 3 days ago) · 10 languages

21 raw signals (11 security + 10 graph) 0th percentile · Javascript · tiny (<2K LoC) System graph score 90 (lower by 50)

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

Complete repo analysis

Last scanned 2 weeks, 3 days ago · v2 · 16 actionable findings from 2 signal sources. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON
Combined
73.1
/100
Security checks
56
11 findings
System graph
91
66.7% cov · 5 findings
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 0.0 0.15 0.00
practices_score 30.0 0.15 4.50
code_quality 70.0 0.10 7.00
Overall 1.00 40.2
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all
Severity: Critical 0 High 0 Medium 7 Low 4 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 11 System graph 5 Crowd 0 Layer: Quality 11 Software 1 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.

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/1d7a26b8-9fda-4a66-9dca-5e1e9efa2178/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/1d7a26b8-9fda-4a66-9dca-5e1e9efa2178/

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.