60
/ 100
Getting some notice. Tests and CI would be the fastest wins.
This add-on adds several Origins and Classes with passive abilities to the game, in which you choose upon the start of your adventure.
A low grade is a to-do list, not a judgment of your code
Most gaps here are documentation, tests, and setup, not the code itself. Closing your top 3 gaps alone would lift this repo to A (92).
See your top fixesTop fixes
Highest-impact changes first, ranked by point weight
- 1Tests18pt
Add automated tests. They prove the code works and give contributors confidence to make changes.
- 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
73
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 MIT.
Engineering
47
No tests detected anywhere in the repository.
→ Add automated tests. They prove the code works and give contributors confidence to make changes.
CI is configured (.github/workflows/build.yml).
Lockfile present (package-lock.json). Installs are reproducible.
Linter or formatter configured (.prettierrc.json).
Issue or PR templates present.
Project health
100
Dependency manifest found (filters/emit_domain/package.json).
Repository has a description.
Actively maintained (pushed within the last month).
.gitignore present.
Repository health signals
Activity, community, and responsiveness at scan time
Activity
- 222 / 383Commits (30d / 90d)
- 7Forks
- 3Releaseslatest 1mo ago
Community
- 57% - FairCommunity health
- -authors own >50% of commits
- 12Watchers
Responsiveness
- 413d 15hMedian issue response
- 21d 12hMedian PR merge time
- 3Open issues
Repository files15 root entries
- .githubGood: CI is configured (.github/workflows/build.yml).Good: Issue or PR templates present.
- .vscode
- filtersGood: Dependency manifest found (filters/emit_domain/package.json).
- packs
- world
- .gitignoreGood: .gitignore present.
- .prettierignore
- .prettierrc.jsonGood: Linter or formatter configured (.prettierrc.json).
- .regolithignore
- config.json
- LICENSEGood: Licensed under MIT.
- OriginsPE.code-workspace
- package-lock.jsonGood: Lockfile present (package-lock.json). Installs are reproducible.
- README.mdGood: README is present.Issue: README has some structure (−7 pts). 2-3 headings earns partial credit; 4+ earns the full +15 pts.Fix: Add more sections (Overview, Install, Usage, Contributing) using ## headings.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.
- title_high_res.png
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/r4isen1920/originspe)