0
/ 100
Good shape overall. A few tweaks would push it into the top tier.
Test suite designed to check compliance with the SystemVerilog standard.
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
82
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 documents how to install the project.
README is present.
Licensed under ISC.
Engineering
71
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.
CI is configured (.github/workflows/lint-review.yml).
Test files detected (conf/report/filter_ui_test.py).
Lockfile present (conf/requirements.txt). Installs are reproducible.
Linter or formatter configured (.editorconfig).
Project health
100
Dependency manifest found (conf/requirements.txt).
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)
- 95Forks
- 0Releases
Community
- -Community health
- -authors own >50% of commits
- 379Watchers
Responsiveness
- 1d 6hMedian issue response
- 6hMedian PR merge time
- 70Open issues
Repository files15 root entries
- .githubGood: CI is configured (.github/workflows/lint-review.yml).Good: Dependabot configured for gitsubmodule.
- confGood: Test files detected (conf/report/filter_ui_test.py).Good: Lockfile present (conf/requirements.txt). Installs are reproducible.Good: Environment pinned via conf/environment.yml.Good: Dependency manifest found (conf/requirements.txt).
- generators
- img
- tests
- third_party
- tools
- .editorconfigGood: Linter or formatter configured (.editorconfig).
- .gitignoreGood: .gitignore present.
- .gitmodules
- .style.yapf
- AUTHORS
- LICENSEGood: Licensed under ISC.
- Makefile
- 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.Good: README includes status badges.Good: README documents how to install the project.Good: README documents how to run the project.
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/chipsalliance/sv-tests)