roypatigayon/milestone_mate

0

/ 100

Documentation76
Engineering86
Health42
JavaScript02y ago
Grade a repo

Solid engineering. The main gap is visibility.

Documentation

76

README12pt55

README is present.

Contributing guide5pt72

CONTRIBUTING guide found.

Install and run instructions9pt90

README documents how to install the project.

License6pt100

A license file is present.

Engineering

86

Issue and PR templates6pt0

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.

Reproducibility6pt82

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

Tests18pt100

Test files detected (backend/node_modules/bcryptjs/tests).

CI/CD14pt100

CI is configured (backend/node_modules/bcryptjs/.travis.yml).

Linting and formatting5pt100

Linter or formatter configured (backend/node_modules/call-bind/.eslintrc).

Project health

42

Activity5pt5

No pushes in over 2 years. Looks unmaintained (−95 pts).

→ A recent commit signals the project is alive and worth using.

Repository metadata5pt40

No repository description set on GitHub (−60 pts).

→ Add a one-line description in the repo Settings → About. It appears in search results and social previews.

Housekeeping3pt60

.gitignore present.

Dependency manifest6pt65

Dependency manifest found (package.json).

Repository health signals

Activity, community, and responsiveness at scan time

Activity

  • —
    Commits (30d / 90d)
  • 0
    Forks
  • 0
    Releases

Community

  • —
    Community health
  • —
    authors own >50% of commits
  • 0
    Watchers

Responsiveness

  • —
    Median issue response
  • —
    Median PR merge time
  • 0
    Open issues
Repository files7 root entries
  • backend
    Good: A license file is present.
    Good: CONTRIBUTING guide found.
    Issue: CONTRIBUTING guide contents could not be read (−28 pts vs a readable file).Fix: Move the file to the repo root or docs/CONTRIBUTING.md so its setup, style, test, and PR sections can be graded.
    Good: Test files detected (backend/node_modules/bcryptjs/tests).
    Good: CI is configured (backend/node_modules/bcryptjs/.travis.yml).
    Good: Linter or formatter configured (backend/node_modules/call-bind/.eslintrc).
    Good: Dependabot is configured. Dependencies update automatically.
    Good: Security policy present.
    Issue: Build artifacts or local files may be committed (backend/node_modules/.bin) (−40 pts).Fix: Remove them and add to .gitignore.
  • public
  • src
  • .gitignore
    Good: .gitignore present.
  • 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.
    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.
    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.