Good shape overall. A few tweaks would push it into the top tier.
Basic Actual Budget API exposed through HTTP endpoints
Documentation
70
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
72
No linter or formatter found.
→ Add ESLint (eslint.config.js) and/or Prettier (.prettierrc), install them as devDependencies, and add a `lint` script to package.json.
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/ci.yml).
Lockfile present (package-lock.json). Installs are reproducible.
Test files detected (__tests__).
Project health
83
.gitignore present.
Dependency manifest found (package.json).
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)
- 48Forks
- 40Releaseslatest 2y ago
Community
- —Community health
- —authors own >50% of commits
- 229Watchers
Responsiveness
- 9hMedian issue response
- 17hMedian PR merge time
- 3Open issues
Repository files18 root entries
- __mocks__
- __tests__Good: Test files detected (__tests__).
- .githubGood: CI is configured (.github/workflows/ci.yml).Good: Dependabot configured for npm.
- examples
- grafana
- src
- .dockerignore
- .envIssue: Build artifacts or local files may be committed (.env) (−40 pts).Fix: Remove them and add to .gitignore.
- .gitignoreGood: .gitignore present.
- docker-compose.yml
- DockerfileGood: Environment pinned via Dockerfile.
- entrypoint.sh
- jest.config.js
- LICENSEGood: Licensed under MIT.
- package-lock.jsonGood: Lockfile present (package-lock.json). Installs are reproducible.
- package.jsonGood: Dependency manifest found (package.json).
- README.mdGood: README is present.Good: README is well structured with multiple sections.Issue: No screenshots or images in the README (−20 pts).Fix: Add a GIF, screenshot, or logo image. It is the fastest way to show what your project does.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.
- server.js