0
/ 100
Some interest. A stronger README and CI would help.
The official wiki repository for OrcaSlicer
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 D (69).
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
32
No install instructions found in the README (−45 pts).
→ Add a section showing how to install dependencies.
No license detected.
→ Add a LICENSE file. Without one, nobody can legally use, copy, or contribute to your code.
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.
Engineering
41
No tests detected anywhere in the repository.
→ Add automated tests. They prove the code works and give contributors confidence to make changes.
No dependency lockfile found (−70 pts).
→ Commit the lockfile for this project's package manager so installs produce the same dependency versions everywhere.
CI is configured (.github/workflows/orphaned_files.yml).
Linter or formatter configured (.editorconfig).
Issue or PR templates present.
Project health
68
No dependency manifest detected at root.
→ Add a manifest (package.json, pyproject.toml, Cargo.toml, go.mod, etc.) so others can install dependencies in one command.
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)
- 42Forks
- 0Releases
Community
- -Community health
- -authors own >50% of commits
- 54Watchers
Responsiveness
- 15hMedian issue response
- <1hMedian PR merge time
- 20Open issues
Repository files25 root entries
- .githubGood: CI is configured (.github/workflows/orphaned_files.yml).Good: Dependabot covers 2 ecosystems (github-actions, docker). Dependencies stay current.Good: Issue or PR templates present.
- .vscode
- calibration
- developer_reference
- general_settings
- guides
- images
- material_settings
- overrides
- print_prepare
- print_settings
- printer_settings
- releases
- user_profiles
- web_extras
- .editorconfigGood: Linter or formatter configured (.editorconfig).
- .gitignoreGood: .gitignore present.
- .markdownlint.json
- build.ps1
- build.sh
- generate_nav.py
- home.md
- mkdocs.yml
- 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.Issue: No install instructions found in the README (−45 pts).Fix: Add a section showing how to install dependencies.Issue: No run or usage instructions found (−45 pts).Fix: Add a section showing how to start or use the project.
- sync-tab-options-to-wiki.ps1
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/orcaslicer/orcaslicer_wiki)