77
/ 100
Good community traction and solid fundamentals. Nearly in the top tier.
A OneNote add-in with simple, yet powerful and useful features
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
76
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 is present.
README documents how to install the project.
Licensed under MPL-2.0.
Engineering
68
No dependency lockfile found (−70 pts).
→ Enable and commit packages.lock.json so NuGet restores are repeatable.
CI is configured (.github/workflows/build.yml).
Test files detected (OneMoreTests/Commands/Clean/ClearBackgroundCommandTests.cs).
.NET formatting configured (.editorconfig).
Issue or PR templates present.
Project health
100
Dependency manifest found (OneMore.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)
- 253Forks
- 209Releaseslatest 6y ago
Community
- 57% - FairCommunity health
- 1 bus factorlowauthor own >50% of commits
- 3,343Watchers
Responsiveness
- 2hMedian issue response
- <1hMedian PR merge time
- 74Open issues
Repository files35 root entries
- .claude
- .githubGood: CI is configured (.github/workflows/build.yml).Good: Issue or PR templates present.
- docs
- OneMore
- OneMoreBundle
- OneMoreCalendar
- OneMoreCli
- OneMoreProtocolHandler
- OneMoreSetup
- OneMoreSetupActions
- OneMoreSmokeTests
- OneMoreTestsGood: Test files detected (OneMoreTests/Commands/Clean/ClearBackgroundCommandTests.cs).
- OneMoreTray
- packers
- Plugins
- Reference
- Templates
- Themes
- .editorconfigGood: .NET formatting configured (.editorconfig).
- .gitattributes
- .gitignoreGood: .gitignore present.
- build.ps1
- CLAUDE.md
- find-unused-resources.ps1
- get-releases.ps1
- iq.ps1
- LICENSEGood: Licensed under MPL-2.0.
- OneMore.slnGood: Dependency manifest found (OneMore.sln).
- README.mdGood: README is present.Good: README is well structured with multiple sections.Good: README includes screenshots or visuals. Great for first impressions.Issue: README has no code examples (−15 pts).Fix: Show a quick-start snippet so contributors can see what using your project looks like.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.
- register-onemore.reg
- setoffice.ps1
- setregistry.ps1
- setversion.ps1
- stop.ps1
- update-sdk.ps1
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/stevencohn/onemore)