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.
Upstream (GitHub) caused delay on this scan — not Repobility.
  • GitHub API rate-limited (HTTP 403) — preflight skipped, fell back to direct git clone.
  • Clone from GitHub took 55.76s for a 179.7 MB repo slow.
  • Repobility's analysis ran in 32.95s after the clone landed.

vm0-ai/vm0

https://github.com/vm0-ai/vm0 · scanned 2026-05-31 01:27 UTC (5 days, 14 hours ago) · 10 languages

1670 findings (261 legacy + 1409 scanner) 11/13 scanners ran 41st percentile · Typescript · huge (>500K LoC) Scanner says 59 (higher by 24)

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 5 days, 14 hours ago · v2 · last Δ -4.4 (diff) · 950 findings from 2 sources. Findings combine the legacy security pipeline AND the multi-layer engine (atlas, wiring, flows, ranked) AND verified AI agent contributions.

JSON
Score breakdown â 2026-05-18-v5
Component Sub-score Weight Contribution
structure_score 40.0 0.15 6.00
security_score 100.0 0.25 25.00
testing_score 100.0 0.20 20.00
documentation_score 98.0 0.15 14.70
practices_score 82.0 0.15 12.30
code_quality 51.0 0.10 5.10
Overall 1.00 83.1
security_score may be inflated — optional security scanners were skipped on this fast scan
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all

Top 10 actions, ranked by impact × ease. Severity drives impact; tag-based fix-clarity drives ease.

#1
Possible secret in crates/vsock-guest/src/user.rs
GapSeverity.CRITICAL Layer.SECURITY score 1.000
Why: critical severity · a leaked credential is a worst-case bug · fix is short / mechanical
Fix: Rotate the credential and remove it from in crates/vsock-guest/src/user.rs:261; move to env var / secrets manager.
crates/vsock-guest/src/user.rs:261
#2
Possible secret in crates/vsock-guest/src/user.rs
GapSeverity.CRITICAL Layer.SECURITY score 1.000
Why: critical severity · a leaked credential is a worst-case bug · fix is short / mechanical
Fix: Rotate the credential and remove it from in crates/vsock-guest/src/user.rs:274; move to env var / secrets manager.
crates/vsock-guest/src/user.rs:274
#3
Possible secret in crates/api-contracts/src/generated/model_providers.rs
GapSeverity.CRITICAL Layer.SECURITY score 1.000
Why: critical severity · a leaked credential is a worst-case bug · fix is short / mechanical
Fix: Rotate the credential and remove it from in crates/api-contracts/src/generated/model_providers.rs:23; move to env var / secrets manager.
crates/api-contracts/src/generated/model_providers.rs:23
#4
Possible secret in turbo/packages/connectors/src/connectors/servicenow.ts
GapSeverity.CRITICAL Layer.SECURITY score 1.000
Why: critical severity · a leaked credential is a worst-case bug · fix is short / mechanical
Fix: Rotate the credential and remove it from in turbo/packages/connectors/src/connectors/servicenow.ts:40; move to env var / secrets manager.
turbo/packages/connectors/src/connectors/servicenow.ts:40
#5
Possible secret in turbo/packages/api-contracts/src/contracts/model-providers.ts
GapSeverity.CRITICAL Layer.SECURITY score 1.000
Why: critical severity · a leaked credential is a worst-case bug · fix is short / mechanical
Fix: Rotate the credential and remove it from in turbo/packages/api-contracts/src/contracts/model-providers.ts:979; move to env var / secrets manager.
turbo/packages/api-contracts/src/contracts/model-providers.ts:979
#6
Possible secret in turbo/packages/api-contracts/src/contracts/model-providers.ts
GapSeverity.CRITICAL Layer.SECURITY score 1.000
Why: critical severity · a leaked credential is a worst-case bug · fix is short / mechanical
Fix: Rotate the credential and remove it from in turbo/packages/api-contracts/src/contracts/model-providers.ts:969; move to env var / secrets manager.
turbo/packages/api-contracts/src/contracts/model-providers.ts:969
#7
Possible secret in turbo/packages/api-contracts/src/contracts/model-providers.ts
GapSeverity.CRITICAL Layer.SECURITY score 1.000
Why: critical severity · a leaked credential is a worst-case bug · fix is short / mechanical
Fix: Rotate the credential and remove it from in turbo/packages/api-contracts/src/contracts/model-providers.ts:982; move to env var / secrets manager.
turbo/packages/api-contracts/src/contracts/model-providers.ts:982
#8
Possible secret in turbo/packages/firewalls-generator/src/cronlytic.ts
GapSeverity.CRITICAL Layer.SECURITY score 1.000
Why: critical severity · a leaked credential is a worst-case bug · fix is short / mechanical
Fix: Rotate the credential and remove it from in turbo/packages/firewalls-generator/src/cronlytic.ts:4; move to env var / secrets manager.
turbo/packages/firewalls-generator/src/cronlytic.ts:4
#9
Possible secret in turbo/packages/firewalls-generator/src/deepseek.ts
GapSeverity.CRITICAL Layer.SECURITY score 1.000
Why: critical severity · a leaked credential is a worst-case bug · fix is short / mechanical
Fix: Rotate the credential and remove it from in turbo/packages/firewalls-generator/src/deepseek.ts:14; move to env var / secrets manager.
turbo/packages/firewalls-generator/src/deepseek.ts:14
#10
Possible secret in turbo/packages/firewalls-generator/src/bland.ts
GapSeverity.CRITICAL Layer.SECURITY score 1.000
Why: critical severity · a leaked credential is a worst-case bug · fix is short / mechanical
Fix: Rotate the credential and remove it from in turbo/packages/firewalls-generator/src/bland.ts:12; move to env var / secrets manager.
turbo/packages/firewalls-generator/src/bland.ts:12

Click "Find this gap" on any action above to jump to it on the Findings tab. Adjust the chip bar to filter by impact (severity), layer, or source.

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/c5e1fbe1-170b-4f36-b3c5-d92f53e41551/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/c5e1fbe1-170b-4f36-b3c5-d92f53e41551/

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.