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

Scan timing: clone 3.21s · analysis 17.05s · 1.2 MB · GitHub API rate-limit (preflight)

tighten/ozzie

https://github.com/tighten/ozzie · scanned 2026-06-05 14:00 UTC (5 days, 6 hours ago) · 10 languages

110 raw signals (84 security + 26 graph) 43rd percentile · Php · small (2-20K LoC) System graph score 86 (lower by 19)

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

Complete repo analysis

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

JSON
Combined
74.4
/100
Security checks
63
78 findings
System graph
86
100.0% cov · 10 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 85.0 0.15 12.75
security_score 36.1 0.25 9.03
testing_score 53.0 0.20 10.60
documentation_score 78.7 0.15 11.80
practices_score 100.0 0.15 15.00
code_quality 80.0 0.10 8.00
Overall 1.00 67.2
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all
Severity: Critical 0 High 21 Medium 36 Low 20 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 78 System graph 10 Crowd 0 Layer: Quality 9 Security 7 Software 60 Cicd 8 Api 1 Frontend 2 Hardware 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 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
  • medium npm package `stylelint-config-standard` is 4 major version(s) behind (36.0.1 ->… package.json
  • low File has no detected symbols: vite.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/0a338e29-8fb6-4f3f-b3f5-e86ed9e386e2/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/0a338e29-8fb6-4f3f-b3f5-e86ed9e386e2/

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.