85
/ 100
Well engineered. The main gaps are CI and a contributing guide.
A modern, fast and flexible .NET testing framework
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 a lint step to catch style issues automatically.
- 4CI/CD14pt
Add `tsc --noEmit`, `mypy`, or `cargo check` to catch type errors before they merge.
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
93
CONTRIBUTING guide found.
README documents how to install the project.
README is present.
Licensed under MIT.
Engineering
79
CI is configured (.github/workflows/deploy-pages-test.yml).
Test files detected (benchmarks/TUnit.PerformanceBenchmarks/Tests).
Lockfile present (docs/yarn.lock). Installs are reproducible.
.NET formatting configured (.editorconfig).
Issue or PR templates present.
Project health
94
.gitignore present.
Dependency manifest found (benchmarks/TUnit.Mocks.Benchmarks/TUnit.Mocks.Benchmarks.csproj).
Repository has a description.
Actively maintained (pushed within the last month).
Repository health signals
Activity, community, and responsiveness at scan time
Activity
- 189 / 508Commits (30d / 90d)
- 138Forks
- 237Releaseslatest 10mo ago
Community
- 71% - FairCommunity health
- 1 bus factorlowauthor own >50% of commits
- 3,968Watchers
Responsiveness
- -Median issue response
- <1hMedian PR merge time
- 14Open issues
Repository files30 root entries
- .claude
- .config
- .devcontainer
- .githubGood: CONTRIBUTING guide found.Issue: CONTRIBUTING guide contents could not be read (−28 pts vs a readable file).Fix: Move the file to the repo root or docs/CONTRIBUTING.md so its setup, style, test, and PR sections can be graded.Good: CI is configured (.github/workflows/deploy-pages-test.yml).Good: Issue or PR templates present.
- .vscode
- assets
- benchmarksGood: Test files detected (benchmarks/TUnit.PerformanceBenchmarks/Tests).Good: Dependency manifest found (benchmarks/TUnit.Mocks.Benchmarks/TUnit.Mocks.Benchmarks.csproj).
- docsGood: Lockfile present (docs/yarn.lock). Installs are reproducible.
- eng
- examples
- scripts
- skills
- srcIssue: Build artifacts or local files may be committed (src/TUnit.Templates/.idea/.idea.TUnit.dir) (−40 pts).Fix: Remove them and add to .gitignore.
- tests
- tools
- .editorconfigGood: .NET formatting configured (.editorconfig).
- .gitattributes
- .gitignoreGood: .gitignore present.
- AGENTS.md
- Directory.Build.props
- Directory.Build.targets
- Directory.Packages.props
- GitVersion.yml
- global.json
- LICENSEGood: Licensed under MIT.
- 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.
- renovate.jsonGood: Renovate is configured (renovate.json). Dependencies update automatically across every package manager it detects.
- TUnit.CI.slnx
- TUnit.Dev.slnx
- TUnit.slnx
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/thomhurst/tunit)