82
/ 100
Well engineered. The main gaps are CI and a reproducible setup.
A .NET library that makes it easier to create beautiful console applications.
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
94
Contributing guide is detailed and thorough.
README documents how to install the project.
README is present.
Licensed under MIT.
Engineering
68
No dependency lockfile found (−70 pts).
→ Enable and commit packages.lock.json so NuGet restores are repeatable.
CI is configured (.github/workflows/ci.yaml).
Test files detected (src/Spectre.Console.Ansi.Tests/AnsiMarkupTests.cs).
.NET formatting configured (.editorconfig).
Issue or PR templates present.
Project health
100
Dependency manifest found (src/Benchmarks/Benchmarks.csproj).
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)
- 674Forks
- 21Releaseslatest 11mo ago
Community
- 87% - GoodCommunity health
- 2 bus factorauthors own >50% of commits
- 11,564Watchers
Responsiveness
- 1d 20hMedian issue response
- <1hMedian PR merge time
- 173Open issues
Repository files20 root entries
- .githubGood: CI is configured (.github/workflows/ci.yaml).Good: Issue or PR templates present.
- resources
- srcGood: Test files detected (src/Spectre.Console.Ansi.Tests/AnsiMarkupTests.cs).Good: Dependency manifest found (src/Benchmarks/Benchmarks.csproj).
- .editorconfigGood: .NET formatting configured (.editorconfig).
- .git-blame-ignore-revs
- .gitattributes
- .gitignoreGood: .gitignore present.
- build.cs
- CODE_OF_CONDUCT.mdGood: Code of conduct present.
- CONTRIBUTING.mdGood: Contributing guide is detailed and thorough.Issue: Contributing guide lacks a setup section (−12 pts).Fix: Show new contributors how to get a local dev environment running.Good: Contributing guide describes code style expectations.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).Good: Contributing guide describes the PR/review workflow.Issue: Contributing guide has no code examples (−5 pts).Fix: Add code blocks showing example commands for setup, running tests, and submitting a PR.
- dotnet-tools.json
- global.json
- LICENSE.mdGood: Licensed under MIT.
- NuGet.Config
- README.fa.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.
- README.jp.md
- README.md
- README.pt-BR.md
- README.tr.md
- README.zh.md
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/spectreconsole/spectre.console)