0
/ 100
Solid engineering. The biggest lever is CI.
gpt-oss-120b and gpt-oss-20b are two open-weight language models by OpenAI
Top fixes
Highest-impact changes first, ranked by point weight
- 1Tests18pt
Wire your tests to a documented command (e.g. a test script in your build config) so the suite is reproducible.
- 2CI/CD14pt
Add a step like `run: npm test`, `run: pytest`, or `run: tox` to your workflow file.
- 3CI/CD14pt
Add `pull_request:` to the workflow `on:` triggers.
- 4CI/CD14pt
Add a lint step to catch style issues automatically.
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.
Scorecard
Every check, grouped by category and sorted worst-first
Documentation
82
Contributing guidance is in the README, not a dedicated CONTRIBUTING.md (−20 pts).
→ Moving it to a CONTRIBUTING.md makes it easier to find and keeps the README focused. A dedicated file earns +47 pts base.
README is present.
README documents how to install the project.
Licensed under Apache-2.0.
Engineering
62
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.
CI is configured (.github/workflows/CI.yml).
Lockfile present (compatibility-test/package-lock.json). Installs are reproducible.
Test files detected (gpt_oss/metal/test).
Issue or PR templates present.
Project health
95
Actively maintained (pushed within 3 months).
Dependency manifest found (pyproject.toml).
Repository has a description.
.gitignore present.
Repository health signals
Activity, community, and responsiveness at scan time
Activity
- 0 / 1Commits (30d / 90d)
- 2,120Forks
- 6Releaseslatest 6mo ago
Community
- 37% - WeakCommunity health
- 6 bus factorauthors own >50% of commits
- 20,238Watchers
Responsiveness
- 14d 15hMedian issue response
- <1hMedian PR merge time
- 94Open issues
Repository files17 root entries
- _build
- .githubGood: CI is configured (.github/workflows/CI.yml).Good: Issue or PR templates present.
- compatibility-testGood: Lockfile present (compatibility-test/package-lock.json). Installs are reproducible.
- docs
- examples
- gpt_ossGood: Test files detected (gpt_oss/metal/test).
- gpt-oss-mcp-server
- tests
- tests-data
- .gitignoreGood: .gitignore present.
- awesome-gpt-oss.md
- CMakeLists.txt
- LICENSEGood: Licensed under Apache-2.0.
- MANIFEST.in
- pyproject.tomlGood: Dependency manifest found (pyproject.toml).
- README.mdGood: 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.
- USAGE_POLICY
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/openai/gpt-oss)