87
/ 100
Well engineered. The main gaps are setup instructions and dependency metadata.
OpenProject is the leading open source project management software for product, project and portfolio management. A powerful Jira alternative with agile planning, issue tracking, roadmaps, Gantt charts, time tracking, collaboration features, and more. Available on premises or in the cloud. ⭐ Star us on GitHub
Top fixes
Highest-impact changes first, ranked by point weight
- 1CI/CD14pt
Add a lint step to catch style issues automatically.
- 2CI/CD14pt
Add `tsc --noEmit`, `mypy`, or `cargo check` to catch type errors before they merge.
- 3CI/CD14pt
Upload coverage to Codecov, Coveralls, or report it with `--coverage` flags.
- 4README12pt
Show a quick-start snippet so contributors can see what using your project looks like.
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
79
README documents how to install the project.
README is present.
Contributing guide is detailed and thorough.
Licensed under GPL-3.0.
Engineering
96
CI is configured (.github/workflows/test-core.yml).
Test files detected (extensions/op-blocknote-hocuspocus/test).
Linter or formatter configured (.editorconfig).
Lockfile present (Gemfile.lock). Installs are reproducible.
Issue or PR templates present.
Project health
79
Dependency manifest found (Gemfile).
.gitignore present.
Repository has a description.
Actively maintained (pushed within the last month).
Repository health signals
Activity, community, and responsiveness at scan time
Activity
- 1223 / 4490Commits (30d / 90d)
- 3,528Forks
- 196Releaseslatest 6y ago
Community
- 100% - GoodCommunity health
- 6 bus factorauthors own >50% of commits
- 16,315Watchers
Responsiveness
- -Median issue response
- 3d 2hMedian PR merge time
- 266Open issues
Repository files75 root entries
- .erb_linters
- .githubGood: CI is configured (.github/workflows/test-core.yml).Good: Dependabot covers 3 ecosystems (npm, bundler, github-actions). Dependencies stay current.Good: Issue or PR templates present.
- .redocly
- app
- bin
- config
- db
- dockerIssue: Build artifacts or local files may be committed (docker/dev/jira-software/.env) (−40 pts).Fix: Remove them and add to .gitignore.
- docs
- extensionsGood: Test files detected (extensions/op-blocknote-hocuspocus/test).
- extra
- files
- frontend
- help
- lib
- lib_static
- log
- lookbook
- modules
- nix
- packaging
- public
- screenshots
- script
- spec
- tmp
- vendor
- vendored-plugins
- .buildpacks
- .dockerignore
- .editorconfigGood: Linter or formatter configured (.editorconfig).
- .env.example
- .env.test.local.example
- .erb_lint.yml
- .git-blame-ignore-revs
- .gitignoreGood: .gitignore present.
- .jshintignore
- .npmrc
- .openproject-token.pub
- .pkgr.yml
- .redocly.lint-ignore.yaml
- .redocly.yaml
- .rspec_parallel
- .rubocop.yml
- .ruby-version
- .yamllint.yml
- AGENTS.md
- CHANGELOG.md
- CLAUDE.md
- CODE_OF_CONDUCT.mdGood: Code of conduct present.
- config.ru
- CONTRIBUTING.mdGood: Contributing guide is detailed and thorough.Issue: Contributing guide lacks a setup section (−12 pts).Fix: Show new contributors how to get a local dev environment running.Issue: Contributing guide lacks a code style section (−8 pts).Fix: Describe your linting/formatting rules and how to run them.Good: Contributing guide explains how to run tests.Good: Contributing guide describes the PR/review workflow.Good: Contributing guide includes code examples.
- COPYRIGHT
- COPYRIGHT_short
- crowdin.yml
- Dangerfile
- docker-compose.ci.yml
- docker-compose.override.example.yml
- docker-compose.ymlGood: Environment pinned via docker-compose.yml.
- GemfileGood: Dependency manifest found (Gemfile).
- Gemfile.lockGood: Lockfile present (Gemfile.lock). Installs are reproducible.
- Gemfile.modules
- GitHub-tab-new.png
- Guardfile
- lefthook.yml
- LICENSEGood: Licensed under GPL-3.0.
- package-lock.json
- package.json
- Procfile
- Procfile.dev
- publiccode_logo.svg
- publiccode.yml
- Rakefile
- 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.Issue: No run or usage instructions found (−45 pts).Fix: Add a section showing how to start or use the project.
- SECURITY.mdGood: Security policy present.
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/opf/openproject)