kenlasko/monize
Grade a repo

84

/ 100

GradeB

Well engineered. The main gaps are test coverage and dependency metadata.

Top 24% of 5,156 graded repos

My unabashedly AI-coded Microsoft Money/Quicken replacement

Documentation93
Engineering76
Health89
TypeScript252AGPL-3.010d ago

Top fixes

Highest-impact changes first, ranked by point weight

9 to address
  1. 1
    Tests18pt

    Set scripts.test in package.json to your actual test command, e.g. "vitest" or "jest".

  2. 2
    README12pt

    Add CI/build status badges from shields.io or your CI provider to signal project health.

  3. 3
    Dependency manifest6pt

    Add a `repository` field pointing to the GitHub URL so npm knows where the source lives.

  4. 4
    Dependency manifest6pt

    Add a `keywords` array to help people find your package on npm.

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.

Install the GitHub App

Scorecard

Every check, grouped by category and sorted worst-first

Documentation

93

Contributing guide5pt80

Contributing guide is detailed and thorough.

README12pt90

README is present.

Install and run instructions9pt100

README documents how to install the project.

License6pt100

Licensed under AGPL-3.0.

Engineering

76

Tests18pt35

Test files detected (backend/scripts/migration-lint.test.mjs).

CI/CD14pt100

CI is configured (.github/workflows/ci.yml).

Linting and formatting5pt100

Linter or formatter configured (backend/eslint.config.mjs).

Reproducibility6pt100

Lockfile present (package-lock.json). Installs are reproducible.

Issue and PR templates6pt100

Issue or PR templates present.

Project health

89

Dependency manifest6pt65

Dependency manifest found (package.json).

Repository metadata5pt100

Repository has a description.

Activity5pt100

Actively maintained (pushed within the last month).

Housekeeping3pt100

.gitignore present.

Repository health signals

Activity, community, and responsiveness at scan time

Activity

  • 902 / 2793
    Commits (30d / 90d)
  • 47
    Forks
  • 269
    Releaseslatest 8mo ago

Community

  • 85% - Good
    Community health
  • 1 bus factorlow
    author own >50% of commits
  • 252
    Watchers

Responsiveness

  • 20h
    Median issue response
  • <1h
    Median PR merge time
  • 8
    Open issues
Repository files35 root entries
  • .agents
  • .claude
  • .github
    Good: CI is configured (.github/workflows/ci.yml).
    Good: Dependabot covers 4 ecosystems (npm, npm, npm, npm). Dependencies stay current.
    Good: Issue or PR templates present.
  • .husky
  • .trail
  • backend
    Good: Test files detected (backend/scripts/migration-lint.test.mjs).
    Good: Linter or formatter configured (backend/eslint.config.mjs).
    Good: Environment pinned via backend/Dockerfile.
  • database
  • docs
  • e2e
  • frontend
  • helm
  • scripts
  • website
  • .dockerignore
  • .env.example
  • .gitignore
    Good: .gitignore present.
  • .hadolint.yaml
  • .lintstagedrc.cjs
  • AGENTS.md
  • build-push-deploy.sh
  • CLAUDE.md
  • CONTAINER_BUILD.md
  • CONTRIBUTING.md
    Good: 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.
    Good: Contributing guide describes code style expectations.
    Issue: Contributing guide lacks a testing section (−8 pts).Fix: Show contributors how to run the test suite (e.g. npm test, pytest, cargo test).
    Good: Contributing guide describes the PR/review workflow.
    Good: Contributing guide includes code examples.
  • docker-compose.demo.yml
  • docker-compose.dev.yml
  • docker-compose.e2e.yml
  • docker-compose.ha.yml
  • docker-compose.prod.yml
  • docker-compose.zap.yml
  • LICENSE
    Good: Licensed under AGPL-3.0.
  • ms_money_portfolio_columns.md
  • package-lock.json
    Good: Lockfile present (package-lock.json). Installs are reproducible.
  • package.json
    Good: Dependency manifest found (package.json).
  • README.md
    Good: 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.
  • SECURITY.md
    Good: Security policy present.
RepoGrade badge preview

Add this badge to your README

It updates automatically each time the repo is re-graded.

[![RepoGrade](https://www.repo-grade.com/api/badge/kenlasko/monize)](https://www.repo-grade.com/report/kenlasko/monize)

More graded TypeScript repos