0
/ 100
A well-known project done right. Strong docs and solid engineering throughout.
A suite of tools to automate software compliance checks.
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 lint step to catch style issues automatically.
- 3CI/CD14pt
Add `tsc --noEmit`, `mypy`, or `cargo check` to catch type errors before they merge.
- 4README12pt
Add CI/build status badges from shields.io or your CI provider to signal project health.
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
82
Contributing guidance is in the README, not a dedicated CONTRIBUTING.md (−20 pts).
→ Moving it to a CONTRIBUTING.md makes it easier to find and keeps the README focused. A dedicated file earns +47 pts base.
README is present.
README documents how to install the project.
Licensed under Apache-2.0.
Engineering
86
Test files detected (advisor/src/test).
Lockfile present (plugins/package-managers/bundler/src/funTest/assets/projects/synthetic/gemspec/Gemfile.lock). Installs are reproducible.
CI is configured (.github/workflows/build-and-test.yml).
Java/Kotlin linting configured (.editorconfig).
Issue or PR templates present.
Project health
94
.gitignore present.
Dependency manifest found (build.gradle.kts).
Repository has a description.
Actively maintained (pushed within the last month).
Repository health signals
Activity, community, and responsiveness at scan time
Activity
- -Commits (30d / 90d)
- 383Forks
- 175Releaseslatest 2y ago
Community
- -Community health
- -authors own >50% of commits
- 2,042Watchers
Responsiveness
- 86dMedian issue response
- 2hMedian PR merge time
- 327Open issues
Repository files57 root entries
- .githubGood: CI is configured (.github/workflows/build-and-test.yml).Good: Issue or PR templates present.
- .ideaIssue: Build artifacts or local files may be committed (.idea/icon.png) (−40 pts).Fix: Remove them and add to .gitignore.
- .run
- advisorGood: Test files detected (advisor/src/test).
- analyzer
- buildSrc
- cli
- cli-helper
- cli-test-launcher
- clients
- detekt-rules
- downloader
- evaluator
- examples
- flox
- gradle
- integrations
- LICENSES
- logos
- model
- notifier
- pluginsGood: Lockfile present (plugins/package-managers/bundler/src/funTest/assets/projects/synthetic/gemspec/Gemfile.lock). Installs are reproducible.
- reporter
- scanner
- scripts
- utils
- version-catalog
- website
- .codecov.yml
- .commitlintrc.yml
- .detekt.yml
- .dockerignore
- .editorconfigGood: Java/Kotlin linting configured (.editorconfig).
- .env.versions
- .gitattributes
- .gitignoreGood: .gitignore present.
- .gitmodules
- .linkspector.yml
- .mailmap
- .markdownlint-cli2.yaml
- .markdownlint.yaml
- .miserc.toml
- .ort.yml
- ADOPTERS.md
- build.gradle.ktsGood: Dependency manifest found (build.gradle.kts).
- DockerfileGood: Environment pinned via Dockerfile.
- gradle.properties
- gradlew
- gradlew.bat
- LICENSEGood: Licensed under Apache-2.0.
- mise.toml
- NOTICE
- qodana.yml
- 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.Issue: No status badges in the README (−10 pts).Fix: Add CI/build status badges from shields.io or your CI provider to signal project health.Good: README documents how to install the project.Good: README documents how to run the project.
- renovate.json
- REUSE.toml
- settings.gradle.kts
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/oss-review-toolkit/ort)