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

Scan timing: clone 7.09s · analysis 22.61s · 14.6 MB · GitHub API rate-limit (preflight)

jdx/mise

https://github.com/jdx/mise · scanned 2026-06-05 23:58 UTC (4 days, 3 hours ago) · 10 languages

256 raw signals (154 security + 102 graph) 19th percentile · Rust · large (100-500K LoC) System graph score 71 (lower by 13)

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

Complete repo analysis

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

JSON
Combined
64.1
/100
Security checks
58
48 findings
System graph
71
100.0% cov · 48 findings
Critical
4
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 30.0 0.25 7.50
testing_score 20.0 0.20 4.00
documentation_score 100.0 0.15 15.00
practices_score 97.0 0.15 14.55
code_quality 42.3 0.10 4.23
Overall 1.00 58.0
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all
Severity: Critical 4 High 15 Medium 17 Low 38 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 48 System graph 48 Crowd 0 Layer: Software 23 Cicd 9 Quality 45 Security 9 Api 1 Frontend 2 Network 1 Hardware 6

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 3 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.
3 matching findings on this repo
  • info npm package `@tsconfig/node24` is patch version(s) behind (^24.0.0 -> 24.0.4) package.json
  • low Very large file: src/config/mod.rs (2998 lines)
  • low Very large file: src/config/config_file/mise_toml.rs (2634 lines)
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/a5fdea63-240b-4284-a302-db36a2a52933/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/a5fdea63-240b-4284-a302-db36a2a52933/

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.