83
/ 100
Good community traction and solid fundamentals. Nearly in the top tier.
FlagGems is an operator library for large language models implemented in the Triton Language.
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 `tsc --noEmit`, `mypy`, or `cargo check` to catch type errors before they merge.
- 4CI/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.
Scorecard
Every check, grouped by category and sorted worst-first
Documentation
88
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.
README is present.
README documents how to install the project.
Licensed under Apache-2.0.
Engineering
73
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/linter.yml).
Test files detected (benchmark/conftest.py).
Lockfile present (benchmark/models_benchmark/requirements.txt). Installs are reproducible.
Issue or PR templates present.
Project health
100
Dependency manifest found (pyproject.toml).
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)
- 424Forks
- 6Releaseslatest 1mo ago
Community
- 87% - GoodCommunity health
- 7 bus factorauthors own >50% of commits
- 1,034Watchers
Responsiveness
- 3hMedian issue response
- 21hMedian PR merge time
- 684Open issues
Repository files36 root entries
- .githubGood: CI is configured (.github/workflows/linter.yml).Good: Dependabot covers 2 ecosystems (pip, github-actions). Dependencies stay current.Good: Issue or PR templates present.
- benchmarkGood: Test files detected (benchmark/conftest.py).Good: Lockfile present (benchmark/models_benchmark/requirements.txt). Installs are reproducible.
- cmake
- conf
- container
- ctests
- docs
- examples
- experimental_tests
- include
- lib
- modules_tests
- requirements
- src
- tests
- tools
- triton_src
- .clang-format
- .coveragerc
- .dockerignore
- .gitattributes
- .gitignoreGood: .gitignore present.
- .gitmodules
- .pre-commit-config.yaml
- CMakeLists.txt
- CODE_OF_CONDUCT.mdGood: Code of conduct present.
- CONTRIBUTING_cn.md
- CONTRIBUTING.mdIssue: 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.Good: Contributing guide includes code examples.
- LICENSEGood: Licensed under Apache-2.0.
- MAINTAINERS.md
- pyproject.tomlGood: Dependency manifest found (pyproject.toml).
- pytest.ini
- README_cn.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.
- README.md
- SECURITY.mdGood: Security policy present.
- setup.sh
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/flagos-ai/flaggems)