lightseekorg/tokenspeed
Grade a repo

80

/ 100

GradeB

Well engineered. The main gaps are linting and CI.

Top 30% of 5,156 graded repos

TokenSpeed is a speed-of-light LLM inference engine.

Documentation87
Engineering71
Health100
Python2,105MIT14d ago

Top fixes

Highest-impact changes first, ranked by point weight

15 to address
  1. 1
    Tests18pt

    Wire your tests to a documented command (e.g. a test script in your build config) so the suite is reproducible.

  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 `tsc --noEmit`, `mypy`, or `cargo check` to catch type errors before they merge.

  4. 4
    CI/CD14pt

    Upload coverage to Codecov, Coveralls, or report it with `--coverage` flags.

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

87

Contributing guide5pt58

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.

README12pt90

README is present.

Install and run instructions9pt90

README documents how to install the project.

License6pt100

Licensed under MIT.

Engineering

71

Linting and formatting5pt0

No linter or formatter config found.

→ Add a linter config such as .eslintrc.json, .prettierrc, ruff.toml, or .golangci.yml to enforce consistent code style.

Reproducibility6pt70

Lockfile present (docs/bun.lock). Installs are reproducible.

CI/CD14pt72

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

Tests18pt80

Test files detected (test).

Issue and PR templates6pt100

Issue or PR templates present.

Project health

100

Dependency manifest6pt100

Dependency manifest found (docs/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)
  • 279
    Forks
  • 1
    Releaseslatest 2mo ago

Community

  • 100% - Good
    Community health
  • 6 bus factor
    authors own >50% of commits
  • 2,105
    Watchers

Responsiveness

  • 7h
    Median issue response
  • 2h
    Median PR merge time
  • 35
    Open issues
Repository files25 root entries
  • .github
    Good: CI is configured (.github/workflows/lint.yml).
    Good: Issue or PR templates present.
  • .skills
  • assets
  • docker
  • docs
    Good: Lockfile present (docs/bun.lock). Installs are reproducible.
    Good: Dependency manifest found (docs/package.json).
  • python
  • test
    Good: Test files detected (test).
  • tokenspeed-kernel
  • tokenspeed-kernel-amd
  • tokenspeed-kernel-npu
  • tokenspeed-mla
  • tokenspeed-scheduler
  • .dockerignore
  • .gitignore
    Good: .gitignore present.
  • .isort.cfg
  • .pre-commit-config.yaml
  • ACKNOWLEDGEMENTS.md
  • AGENTS.md
  • CLAUDE.md
  • CODE_OF_CONDUCT.md
    Good: Code of conduct present.
  • 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).
    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.
    Issue: Contributing guide has no code examples (−5 pts).Fix: Add code blocks showing example commands for setup, running tests, and submitting a PR.
  • GOVERNANCE.md
  • LICENSE
    Good: Licensed under MIT.
  • 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.
    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.
    Good: README documents how to install the project.
    Good: README documents how to run the project.
  • SECURITY.md
    Good: Security policy present.
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/lightseekorg/tokenspeed)](https://www.repo-grade.com/report/lightseekorg/tokenspeed)

More graded Python repos