isaacs/node-glob
Grade a repo

84

/ 100

GradeB

A well-known project done right. Strong docs and solid engineering throughout.

Top 22% of 5,156 graded repos

glob functionality for node.js

Documentation87
Engineering80
Health92
TypeScript8,712Other1mo ago

Top fixes

Highest-impact changes first, ranked by point weight

17 to address
  1. 1
    CI/CD14pt

    Add a lint step to catch style issues automatically.

  2. 2
    CI/CD14pt

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

  3. 3
    CI/CD14pt

    Upload coverage to Codecov, Coveralls, or report it with `--coverage` flags.

  4. 4
    README12pt

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

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

87

Contributing guide5pt60

CONTRIBUTING guide is very brief (−12 pts for depth). 150+ words earns +6 pts; 400+ earns +12 pts.

→ Add setup instructions, code style notes, and how to run tests.

README12pt90

README is present.

Install and run instructions9pt90

README documents how to install the project.

License6pt100

Licensed under Other.

Engineering

80

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.

Reproducibility6pt70

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

CI/CD14pt85

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

Tests18pt100

Test files detected (tap-snapshots/test).

Linting and formatting5pt100

Linter or formatter configured (.prettierrc.json).

Project health

92

Dependency manifest6pt75

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

  • 2 / 8
    Commits (30d / 90d)
  • 533
    Forks
  • 0
    Releases

Community

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

Responsiveness

  • 13h
    Median issue response
  • 1d 6h
    Median PR merge time
  • 3
    Open issues
Repository files28 root entries
  • .github
    Good: CI is configured (.github/workflows/ci.yml).
  • .tshy
  • examples
  • logo
  • scripts
  • src
  • tap-snapshots
    Good: Test files detected (tap-snapshots/test).
  • test
  • .gitignore
    Good: .gitignore present.
  • .oxlint.json
  • .prettierignore
  • .prettierrc.json
    Good: Linter or formatter configured (.prettierrc.json).
  • .taprc
  • AGENTS.md
  • benchclean.cjs
  • benchmark.sh
  • changelog.md
  • CONTRIBUTING.md
    Issue: CONTRIBUTING guide is very brief (−12 pts for depth). 150+ words earns +6 pts; 400+ earns +12 pts.Fix: Add setup instructions, code style notes, and how to run tests.
    Issue: Contributing guide lacks a setup section (−12 pts).Fix: Show new contributors how to get a local dev environment running.
    Issue: Contributing guide lacks a code style section (−8 pts).Fix: Describe your linting/formatting rules and how to run them.
    Good: Contributing guide explains how to run tests.
    Issue: Contributing guide lacks a PR workflow section (−8 pts).Fix: Explain how to fork, branch, and open a pull request so contributors know what to expect.
    Good: Contributing guide includes code examples.
  • LICENSE.md
    Good: Licensed under Other.
  • make-benchmark-fixture.sh
  • oh-my-glob.gif
  • package-lock.json
    Good: Lockfile present (package-lock.json). Installs are reproducible.
  • package.json
    Good: Dependency manifest found (package.json).
  • patterns.sh
  • prof.sh
  • 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.
  • tsconfig.json
  • typedoc.json
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/isaacs/node-glob)](https://www.repo-grade.com/report/isaacs/node-glob)

More graded TypeScript repos