Good community traction and solid fundamentals. Nearly in the top tier.
TokenSpeed is a speed-of-light LLM inference engine.
Documentation
70
No CONTRIBUTING.md found (−47 pts base + up to −53 pts more for content).
→ Add a CONTRIBUTING.md telling newcomers how to get involved. Include setup, code style, test, and PR instructions.
README is present.
README documents how to install the project.
Licensed under MIT.
Engineering
80
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.
Test files detected (test).
Lockfile present (docs/bun.lock). Installs are reproducible.
CI is configured (.github/workflows/lint.yml).
Issue or PR templates present.
Project health
100
Dependency manifest found (docs/package.json).
Repository has a description.
Actively maintained (pushed within the last month).
.gitignore present.
Repository health signals
Activity, community, and responsiveness at scan time
Activity
- —Commits (30d / 90d)
- 167Forks
- 0Releases
Community
- —Community health
- —authors own >50% of commits
- 1,482Watchers
Responsiveness
- 3hMedian issue response
- 2hMedian PR merge time
- 45Open issues
Repository files20 root entries
- .githubGood: CI is configured (.github/workflows/lint.yml).Good: Issue or PR templates present.
- .skills
- assets
- dockerGood: Environment pinned via docker/Dockerfile.
- docsGood: Lockfile present (docs/bun.lock). Installs are reproducible.Good: Dependency manifest found (docs/package.json).
- python
- testGood: Test files detected (test).
- tokenspeed-kernel
- tokenspeed-kernel-amd
- tokenspeed-mla
- tokenspeed-scheduler
- .dockerignore
- .gitignoreGood: .gitignore present.
- .isort.cfg
- .pre-commit-config.yaml
- ACKNOWLEDGEMENTS.md
- AGENTS.md
- CLAUDE.md
- LICENSEGood: Licensed under MIT.
- README.mdGood: README is present.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.Good: README documents how to install the project.Good: README documents how to run the project.