0
/ 100
Popular for its size, but the engineering basics lag behind the interest.
Open Paper is a workbench for managing your research library. Read, annotate, and understand your papers all in one place. Use an AI assistant to conduct your literature review.
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 B (84).
See your top fixesTop 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 `pull_request:` to the workflow `on:` triggers.
- 4CI/CD14pt
Add a lint step to catch style issues automatically.
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
62
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.
No install instructions found in the README (−45 pts).
→ Add a section showing how to install dependencies.
README is present.
Licensed under AGPL-3.0.
Engineering
61
No issue or PR templates found (−100 pts).
→ Add .github/ISSUE_TEMPLATE/ with bug_report.md and feature_request.md to guide contributors. It dramatically improves issue quality.
CI is configured (.github/workflows/dockerize.yml).
Test files detected (server/tests).
Lockfile present (client/yarn.lock). Installs are reproducible.
Linter or formatter configured (client/eslint.config.mjs).
Project health
100
Dependency manifest found (client/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
- -Commits (30d / 90d)
- 54Forks
- 0Releases
Community
- -Community health
- -authors own >50% of commits
- 360Watchers
Responsiveness
- 3hMedian issue response
- 8hMedian PR merge time
- 2Open issues
Repository files11 root entries
- .githubGood: CI is configured (.github/workflows/dockerize.yml).
- clientGood: Linter or formatter configured (client/eslint.config.mjs).Good: Lockfile present (client/yarn.lock). Installs are reproducible.Good: Environment pinned via client/Dockerfile.Good: Dependency manifest found (client/package.json).
- jobs
- serverGood: Test files detected (server/tests).
- .gitattributes
- .gitignoreGood: .gitignore present.
- .pre-commit-config.yaml
- demo.gif
- DEVELOPMENT.md
- LICENSEGood: Licensed under AGPL-3.0.
- 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.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.Issue: No install instructions found in the README (−45 pts).Fix: Add a section showing how to install dependencies.Good: README documents how to run the project.
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/khoj-ai/openpaper)