computesdk/benchmarks
Grade a repo

56

/ 100

GradeD

A workable base with real gaps. Start with test coverage and CI.

Higher than 45% of 5,156 graded repos

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

Documentation79
Engineering39
Health86
TypeScript102MIT1mo ago

A low grade is a to-do list, not a judgment of your code

Most gaps here are documentation, tests, and setup, not the code itself. Closing your top 3 gaps alone would lift this repo to B (80).

See your top fixes
Now
D
61
Potential
B
80

Top fixes

Highest-impact changes first, ranked by point weight

19 to address
  1. 1
    Tests18pt

    Set scripts.test in package.json to your actual test command, e.g. "vitest" or "jest".

  2. 2
    CI/CD14pt

    Add a step like `run: npm test`, `run: pytest`, or `run: tox` to your workflow file.

  3. 3
    CI/CD14pt

    Add a lint step to catch style issues automatically.

  4. 4
    CI/CD14pt

    Add `tsc --noEmit`, `mypy`, or `cargo check` to catch type errors before they merge.

Working through the fixes? Let every push regrade itself.

The free GitHub App rescans this repo on every push and posts the grade as a commit check, so the score climbs without coming back to rescan by hand.

Install the GitHub App

Scorecard

Every check, grouped by category and sorted worst-first

Documentation

79

Install and run instructions9pt55

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

→ Add a section showing how to install dependencies.

Contributing guide5pt80

Contributing guide is detailed and thorough.

README12pt85

README is present.

License6pt100

Licensed under MIT.

Engineering

39

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.

Tests18pt35

Test files detected (packages/benchsdk-runner/src/__tests__).

CI/CD14pt57

CI is configured (.github/workflows/ci.yml).

Reproducibility6pt80

Lockfile present (pnpm-lock.yaml). 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)
  • 52
    Forks
  • 0
    Releases

Community

  • 62% - Fair
    Community health
  • 2 bus factor
    authors own >50% of commits
  • 102
    Watchers

Responsiveness

  • <1h
    Median issue response
  • <1h
    Median PR merge time
  • 26
    Open issues
Repository files38 root entries
  • .agents
  • .changeset
  • .claude
  • .github
    Good: CI is configured (.github/workflows/ci.yml).
  • benchmarks
    Good: Environment pinned via benchmarks/scale/Dockerfile.
  • packages
    Good: Test files detected (packages/benchsdk-runner/src/__tests__).
  • results
  • sponsors
  • .dockerignore
  • .gitignore
    Good: .gitignore present.
  • AI_GATEWAYS.md
  • ai-gateway.svg
  • browser-throughput.svg
  • browser.svg
  • burst_tti.svg
  • CONTRIBUTING.md
    Good: Contributing guide is detailed and thorough.
    Issue: Contributing guide lacks a setup section (−12 pts).Fix: Show new contributors how to get a local dev environment running.
    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.
  • dax.svg
  • LICENSE
    Good: Licensed under MIT.
  • llms.txt
  • METHODOLOGY.md
  • one-hundred-k-mvp-plan.md
  • package.json
    Good: Dependency manifest found (package.json).
  • pnpm-lock.yaml
    Good: Lockfile present (pnpm-lock.yaml). Installs are reproducible.
  • pnpm-workspace.yaml
  • 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.
    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.
    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
  • snapshot_fork_small.svg
  • SPONSORSHIP.md
  • staggered_tti.svg
  • storage_10mb.svg
  • storage_16mb.svg
  • storage_1mb.svg
  • storage_4mb.svg
  • THROUGHPUT.md
  • tsconfig.json
RepoGrade badge preview

Add this badge to your README

It updates automatically each time the repo is re-graded.

[![RepoGrade](https://www.repo-grade.com/api/badge/computesdk/benchmarks)](https://www.repo-grade.com/report/computesdk/benchmarks)

More graded TypeScript repos