How E2B Runtime scored an A.
A way.space signal summary built from public evidence. It is not a user rating, and not a safety certification. How scores are calculated.
01 / Breakdown
Derived from GitHub, not voted.
GitHub credibility score
code
85/100- ✓ Contributors & bus-factor: 21 recent contributors
- ✓ Commit recency: last commit 0d ago
- ✓ Commit cadence: 838 commits in 90 days
- ✓ Issue close ratio: 76% of issues closed
- ✓ Release cadence: 40 releases in 12 months
- ✓ Stars (log-damped): 1,754 stars (log-damped)
- – Star authenticity: star-velocity check unavailable — GitHub no longer publishes stargazer timestamps for this repo
- – Dependent repos: not measurable — no package listing on a registry we can query
identity
80/100- ✓ Organisation: Built by E2B · notable organization (verified: Org profile shows a Verified badge for e2b.dev; profile website https://e2b.dev/docs, display name "E2B | Cloud for AI Agents", description "Open-source, secure environment with real-world tools for enterprise-grade agents.".)
audits
Not measured- – Third-party scans: not measurable — no registry listings for this tool
freshness
100/100- ✓ Last shipped: last commit 0d ago — standard-churn platforms are expected to ship about every 120d
community
23/100- – Recommends: no recommends from gate-passing builders yet
- ✓ Hacker News mentions: 1 Hacker News story pointing at this tool
- – Signal depth: sparse data — this is an early reading from very few data points
Identity and Community did not lower this score. Identity and Community can only ever add. They did not raise the average for E2B Runtime, so the score shown is the one it would have without them. The components are still listed above, with their real values.
Components that could not be measured are left out of the average entirely, and their weight is redistributed, never scored as zero. Identity and Community are left out the same way when they would not have raised the score. How scores are calculated.