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.41s · analysis 6.51s · 4.2 MB · GitHub API rate-limit (preflight)

e2b-dev/E2B

https://github.com/e2b-dev/E2B · scanned 2026-05-31 01:23 UTC (5 days, 14 hours ago) · 10 languages

661 findings (208 legacy + 453 scanner) 87th percentile · Python · medium (20-100K LoC) Scanner says 73 (higher by 8)

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

Complete repo analysis

Last scanned 5 days, 14 hours ago · v2 · 436 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
Combined
75.2
/100
Repobility
77
208 legacy
9-layer
73
100.0% cov · 228 gaps
Critical
7
click to filter
Agents
6
0 votes
Crowd
0
reported
Score breakdown â 2026-05-18-v5
Component Sub-score Weight Contribution
structure_score 60.0 0.15 9.00
security_score 89.6 0.25 22.40
testing_score 100.0 0.20 20.00
documentation_score 79.0 0.15 11.85
practices_score 84.0 0.15 12.60
code_quality 54.1 0.10 5.41
Overall 1.00 81.3
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all
Severity: Critical 7 High 144 Medium 53 Low 198 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Legacy 208 9-layer 228 Crowd 0 Layer: Quality 193 Cicd 71 Software 134 Security 3 Frontend 32 Hardware 3

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

#1
Docker base image uses a mutable or implicit tag: ubuntu:latest
GapSeverity.MEDIUM Layer.HARDWARE score 0.225
Why: medium severity
packages/cli/testground/demo-basic/Dockerfile:1
#2
GitHub Action is tag-pinned rather than SHA-pinned
GapSeverity.MEDIUM Layer.CICD score 0.225
Why: medium severity
.github/workflows/js_sdk_tests.yml:34
#3
GitHub Action is tag-pinned rather than SHA-pinned
GapSeverity.MEDIUM Layer.CICD score 0.225
Why: medium severity
.github/workflows/js_sdk_tests.yml:41
#4
GitHub Action is tag-pinned rather than SHA-pinned
GapSeverity.MEDIUM Layer.CICD score 0.225
Why: medium severity
.github/workflows/js_sdk_tests.yml:91
#5
GitHub Action is tag-pinned rather than SHA-pinned
GapSeverity.MEDIUM Layer.CICD score 0.225
Why: medium severity
.github/workflows/js_sdk_tests.yml:100
#6
GitHub Action is tag-pinned rather than SHA-pinned
GapSeverity.MEDIUM Layer.CICD score 0.225
Why: medium severity
.github/workflows/cli_tests.yml:33
#7
GitHub Action is tag-pinned rather than SHA-pinned
GapSeverity.MEDIUM Layer.CICD score 0.225
Why: medium severity
.github/workflows/cli_tests.yml:40
#8
GitHub Action is tag-pinned rather than SHA-pinned
GapSeverity.MEDIUM Layer.CICD score 0.225
Why: medium severity
.github/workflows/publish_packages.yml:32
#9
GitHub Action is tag-pinned rather than SHA-pinned
GapSeverity.MEDIUM Layer.CICD score 0.225
Why: medium severity
.github/workflows/publish_packages.yml:44
#10
GitHub Action is tag-pinned rather than SHA-pinned
GapSeverity.MEDIUM Layer.CICD score 0.225
Why: medium severity
.github/workflows/publish_packages.yml:81

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/40abc3d1-0134-4adb-a0b0-f6d2e010ea31/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/40abc3d1-0134-4adb-a0b0-f6d2e010ea31/

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.