computesdk/benchmarks

0

/ 100

Documentation83
Engineering26
Health86
TypeScript82MIT1d ago
Grade a repo

Getting some notice. Tests and CI would be the fastest wins.

Compare startup time-to-interactive for top sandbox providers.

Documentation

83

Install and run instructions9pt45

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

→ Add a section showing how to install dependencies.

Contributing guide5pt92

Contributing guide is detailed and thorough.

README12pt100

README is present.

License6pt100

Licensed under MIT.

Engineering

26

Tests18pt0

No tests detected anywhere in the repository.

→ Add automated tests. They prove the code works and give contributors confidence to make changes.

Linting and formatting5pt0

No linter or formatter found.

→ Add ESLint (eslint.config.js) and/or Prettier (.prettierrc), install them as devDependencies, and add a `lint` script to package.json.

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.

CI/CD14pt57

CI is configured (.github/workflows/pricing-svg.yml).

Reproducibility6pt80

Lockfile present (package-lock.json). Installs are reproducible.

Project health

86

Dependency manifest6pt55

Dependency manifest found (package.json).

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)
  • 24
    Forks
  • 0
    Releases

Community

  • —
    Community health
  • —
    authors own >50% of commits
  • 82
    Watchers

Responsiveness

  • <1h
    Median issue response
  • <1h
    Median PR merge time
  • 18
    Open issues
Repository files30 root entries
  • .claude
  • .github
    Good: CI is configured (.github/workflows/pricing-svg.yml).
  • dist
  • results
  • scripts
  • sponsors
  • src
    Good: Environment pinned via src/scale/Dockerfile.
  • .dockerignore
  • .gitignore
    Good: .gitignore present.
  • browser.svg
  • burst_tti.svg
  • CONTRIBUTING.md
    Good: Contributing guide is detailed and thorough.
    Good: Contributing guide includes setup/install instructions.
    Good: Contributing guide describes code style expectations.
    Good: Contributing guide explains how to run tests.
    Issue: Contributing guide lacks a PR workflow section (−8 pts).Fix: Explain how to fork, branch, and open a pull request so contributors know what to expect.
    Good: Contributing guide includes code examples.
  • env.example
  • LICENSE
    Good: Licensed under MIT.
  • METHODOLOGY.md
  • one-hundred-k-mvp-plan.md
  • package-lock.json
    Good: Lockfile present (package-lock.json). Installs are reproducible.
  • package.json
    Good: Dependency manifest found (package.json).
  • pricing.json
  • pricing.svg
  • README.md
    Good: README is present.
    Good: README is well structured with multiple sections.
    Good: README includes screenshots or visuals. Great for first impressions.
    Good: README has code examples.
    Good: README links to a live demo or deployed app.
    Good: README includes status badges.
    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.
  • results.svg
  • sequential_tti.svg
  • SPONSORSHIP.md
  • staggered_tti.svg
  • storage_10mb.svg
  • storage_16mb.svg
  • storage_1mb.svg
  • storage_4mb.svg
  • tsconfig.json