0
/ 100
Good shape overall. A few tweaks would push it into the top tier.
All content for ParticularDocs
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 Other.
Engineering
57
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.
No dependency lockfile found (−70 pts).
→ Enable and commit packages.lock.json so NuGet restores are repeatable.
CI is configured (.github/workflows/build-samples-and-snippets.yml).
Test files detected (Snippets/MsmqTransport/MsmqTransport_All/ErrorQueue/Tests.cs).
.NET formatting configured (.editorconfig).
Project health
100
Dependency manifest found (Snippets/ABSDataBus/ABSDataBus.sln).
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)
- 297Forks
- 0Releases
Community
- -Community health
- -authors own >50% of commits
- 108Watchers
Responsiveness
- 139d 1hMedian issue response
- 7hMedian PR merge time
- 136Open issues
Repository files40 root entries
- .devcontainerGood: Environment pinned via .devcontainer/Dockerfile.
- .githubGood: CI is configured (.github/workflows/build-samples-and-snippets.yml).
- .vscode
- architecture
- components
- get-started
- menu
- modernization
- monitoring
- nservicebus
- persistence
- platformGood: 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.
- samples
- security-advisories
- servicecontrol
- serviceinsight
- servicepulse
- shape-the-future
- SnippetsGood: Licensed under Other.Good: Test files detected (Snippets/MsmqTransport/MsmqTransport_All/ErrorQueue/Tests.cs).Good: Dependency manifest found (Snippets/ABSDataBus/ABSDataBus.sln).
- tests
- tools
- transportsGood: Security policy present.
- tutorials
- .editorconfigGood: .NET formatting configured (.editorconfig).
- .gitattributes
- .gitignoreGood: .gitignore present.
- .markdownlint.json
- .prettierignore
- AGENTS.md
- BannedSymbols.txt
- calls-to-action.yaml
- CLAUDE.md
- Directory.Build.props
- GEMINI.md
- global.json
- license.md
- nuget.config
- partials.png
- 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.
- tabbed_snippets.png
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/particular/docs.particular.net)