julianpoy/recipesage
Grade a repo

0

/ 100

GradeD

Popular for its size, but the engineering basics lag behind the interest.

Higher than 48% of 5,156 graded repos

A Collaborative Recipe Keeper, Meal Planner, and Shopping List Organizer in PWA form.

Documentation57
Engineering63
Health79
TypeScript9031mo ago

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 (85).

See your top fixes
Now
D
64
Potential
B
85

Top fixes

Highest-impact changes first, ranked by point weight

19 to address
  1. 1
    Tests18pt

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

  2. 2
    CI/CD14pt

    Add a step like `run: npm test`, `run: pytest`, or `run: tox` to your workflow file.

  3. 3
    CI/CD14pt

    Add a lint step to catch style issues automatically.

  4. 4
    CI/CD14pt

    Add `tsc --noEmit`, `mypy`, or `cargo check` to catch type errors before they merge.

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

57

License6pt0

No license detected.

→ Add a LICENSE file. Without one, nobody can legally use, copy, or contribute to your code.

Contributing guide5pt25

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.

README12pt75

README is present.

Install and run instructions9pt90

README documents how to install the project.

Engineering

63

Tests18pt35

Test files detected (packages/backend/src/models/recipe.spec.js).

CI/CD14pt57

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

Reproducibility6pt92

Lockfile present (pnpm-lock.yaml). Installs are reproducible.

Linting and formatting5pt100

Linter or formatter configured (.editorconfig).

Issue and PR templates6pt100

Issue or PR templates present.

Project health

79

Dependency manifest6pt55

Dependency manifest found (package.json).

Housekeeping3pt60

.gitignore present.

Repository metadata5pt100

Repository has a description.

Activity5pt100

Actively maintained (pushed within the last month).

Repository health signals

Activity, community, and responsiveness at scan time

Activity

  • -
    Commits (30d / 90d)
  • 90
    Forks
  • 450
    Releaseslatest 7y ago

Community

  • -
    Community health
  • -
    authors own >50% of commits
  • 903
    Watchers

Responsiveness

  • 34d 5h
    Median issue response
  • <1h
    Median PR merge time
  • 20
    Open issues
Repository files32 root entries
  • .circleci
  • .githooks
  • .github
    Good: CI is configured (.github/workflows/codeql.yml).
    Good: Dependabot configured for npm.
    Good: Issue or PR templates present.
  • .husky
  • .vscode
  • Assets
  • docs
  • fonts
  • nginx
  • packages
    Good: Test files detected (packages/backend/src/models/recipe.spec.js).
  • scripts
  • twa
    Issue: Build artifacts or local files may be committed (twa/.idea/encodings.xml) (−40 pts).Fix: Remove them and add to .gitignore.
  • .dockerignore
  • .editorconfig
    Good: Linter or formatter configured (.editorconfig).
  • .gitignore
    Good: .gitignore present.
  • .npmrc
  • .nvmrc
  • .prettierignore
  • .prettierrc.json
  • docker-compose.yml
  • Dockerfile
    Good: Environment pinned via Dockerfile.
  • eslint.config.mjs
  • example.env
  • nx.json
  • package.json
    Good: Dependency manifest found (package.json).
  • pnpm-lock.yaml
    Good: Lockfile present (pnpm-lock.yaml). Installs are reproducible.
  • prisma.config.ts
  • production.Dockerfile
  • README.md
    Good: 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.
    Good: README documents how to install the project.
    Good: README documents how to run the project.
  • SECURITY.md
    Good: Security policy present.
  • tsconfig.base.json
  • vitest.workspace.ts
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/julianpoy/recipesage)](https://www.repo-grade.com/report/julianpoy/recipesage)

More graded TypeScript repos