e2b-dev/infra

0

/ 100

Documentation66
Engineering73
Health100
Go1,183Apache-2.01d ago
Grade a repo

Good community traction and solid fundamentals. Nearly in the top tier.

Infrastructure that's powering E2B Cloud.

Documentation

66

Install and run instructions9pt55

No install instructions found in the README (−45 pts).

→ Add a section showing how to install dependencies.

README12pt58

README is present.

Contributing guide5pt61

Contributing guide is too short for full depth credit (−6 pts). 400+ words earns the full +12 pts.

→ Add setup instructions, code style notes, and how to run tests.

License6pt100

Licensed under Apache-2.0.

Engineering

73

Issue and PR templates6pt0

No issue or PR templates found (−100 pts).

→ Add .github/ISSUE_TEMPLATE/ with bug_report.md and feature_request.md to guide contributors. It dramatically improves issue quality.

Tests18pt80

Test files detected (packages/api/internal/api/spec_test.go).

Reproducibility6pt80

Lockfile present (packages/api/go.sum). Installs are reproducible.

CI/CD14pt83

CI is configured (.github/workflows/build-and-upload-images.yml).

Linting and formatting5pt100

Linter or formatter configured (.editorconfig).

Project health

100

Dependency manifest6pt100

Dependency manifest found (go.work).

Repository metadata5pt100

Repository has a description.

Activity5pt100

Actively maintained (pushed within the last month).

Housekeeping3pt100

.gitignore present.

Repository health signals

Activity, community, and responsiveness at scan time

Activity

  • —
    Commits (30d / 90d)
  • 344
    Forks
  • 46
    Releaseslatest 8mo ago

Community

  • —
    Community health
  • —
    authors own >50% of commits
  • 1,183
    Watchers

Responsiveness

  • 113d 17h
    Median issue response
  • 7h
    Median PR merge time
  • 110
    Open issues
Repository files35 root entries
  • .cursor
  • .devcontainer
  • .gemini
  • .github
    Good: CI is configured (.github/workflows/build-and-upload-images.yml).
  • .vscode
  • fixtures
  • iac
  • packages
    Good: Test files detected (packages/api/internal/api/spec_test.go).
    Good: Lockfile present (packages/api/go.sum). Installs are reproducible.
    Good: Environment pinned via packages/api/Dockerfile.
  • readme-assets
    Good: README is present.
    Issue: README is fairly short (−10 pts). At 400+ chars you get partial credit; 1,500+ earns the full +20 pts.Fix: Expand with a description, install steps, usage, and examples.
    Issue: README has some structure (−7 pts). 2-3 headings earns partial credit; 4+ earns the full +15 pts.Fix: Add more sections (Overview, Install, Usage, Contributing) using ## headings.
    Good: README includes screenshots or visuals. Great for first impressions.
    Issue: README has no code examples (−15 pts).Fix: Show a quick-start snippet so contributors can see what using your project looks like.
    Good: README links to a live demo or deployed app.
    Issue: No status badges in the README (−10 pts).Fix: Add CI/build status badges from shields.io or your CI provider to signal project health.
    Issue: No install instructions found in the README (−45 pts).Fix: Add a section showing how to install dependencies.
    Good: README documents how to run the project.
  • scripts
  • spec
  • tests
  • .dockerignore
  • .editorconfig
    Good: Linter or formatter configured (.editorconfig).
  • .env.aws.template
  • .env.gcp.template
  • .envrc
  • .gitattributes
  • .gitignore
    Good: .gitignore present.
  • .golangci.yml
  • .mockery.yaml
  • .tool-versions
  • AGENTS.md
  • CLAUDE.md
  • codecov.yml
  • CODEOWNERS
  • CONTRIBUTING.md
    Issue: Contributing guide is too short for full depth credit (−6 pts). 400+ words earns the full +12 pts.Fix: Add setup instructions, code style notes, and how to run tests.
    Issue: Contributing guide lacks a setup section (−12 pts).Fix: Show new contributors how to get a local dev environment running.
    Issue: Contributing guide lacks a code style section (−8 pts).Fix: Describe your linting/formatting rules and how to run them.
    Issue: Contributing guide lacks a testing section (−8 pts).Fix: Show contributors how to run the test suite (e.g. npm test, pytest, cargo test).
    Good: Contributing guide describes the PR/review workflow.
    Issue: Contributing guide has no code examples (−5 pts).Fix: Add code blocks showing example commands for setup, running tests, and submitting a PR.
  • DEV-LOCAL.md
  • DEV.md
  • go.work
    Good: Dependency manifest found (go.work).
  • LICENSE
    Good: Licensed under Apache-2.0.
  • Makefile
  • README.md
  • redocly.yaml
  • self-host.md