52

/ 100

GradeF

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

Higher than 37% of 5,156 graded repos

📖 The Lessons for every language

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 C (79).

See your top fixes
Now
F
52
Potential
C
79

Top fixes

Highest-impact changes first, ranked by point weight

18 to address
  1. 1
    Tests18pt

    Add automated tests. They prove the code works and give contributors confidence to make changes.

  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

63

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.

Install and run instructions9pt45

No install instructions found in the README (−45 pts).

→ Add a section showing how to install dependencies.

README12pt75

README is present.

License6pt100

Licensed under MIT.

Engineering

30

Tests18pt0

No tests detected anywhere in the repository.

→ Add automated tests. They prove the code works and give contributors confidence to make changes.

Linting and formatting5pt0

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.

Reproducibility6pt10

No dependency lockfile found (−70 pts).

→ Commit package-lock.json, pnpm-lock.yaml, yarn.lock, or bun.lock so Node installs are repeatable.

CI/CD14pt57

CI is configured (.github/workflows/aggregate-audio.yml).

Issue and PR templates6pt100

Issue or PR templates present.

Project health

91

Dependency manifest6pt72

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

  • 132 / 555
    Commits (30d / 90d)
  • 126
    Forks
  • 0
    Releases

Community

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

Responsiveness

  • 12h
    Median issue response
  • 20h
    Median PR merge time
  • 15
    Open issues
Repository files28 root entries
  • .github
    Good: CI is configured (.github/workflows/aggregate-audio.yml).
    Good: Issue or PR templates present.
  • images
  • runners
  • src
  • web
  • .dockerignore
  • .gitignore
    Good: .gitignore present.
  • .npmrc
  • config.js
  • create.js
  • deploy-audio.js
  • deploy-creds.tar.gpg
  • deploy-helper.js
  • deploy-pdf.js
  • deploy-video.js
  • deploy.js
  • docker.gpg
  • Dockerfile
    Good: Environment pinned via Dockerfile.
  • entrypoint.sh
  • LICENSE.md
    Good: Licensed under MIT.
  • package.json
    Good: Dependency manifest found (package.json).
  • port-to-v3.js
  • 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.
    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.
  • run.sh
  • summary.js
  • summary.md
  • verify.js
  • video-links.txt
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/adventech/sabbath-school-lessons)](https://www.repo-grade.com/report/adventech/sabbath-school-lessons)

More graded JavaScript repos