81

/ 100

GradeB

Popular and well-maintained. A little polish away from elite status.

Top 30% of 5,156 graded repos

The official MongoDB Node.js driver

TypeScript10,180Apache-2.01mo ago

Top fixes

Highest-impact changes first, ranked by point weight

11 to address
  1. 1
    Tests18pt

    Wire your tests to a documented command (e.g. a test script in your build config) so the suite is reproducible.

  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

73

Install and run instructions9pt45

README documents how to install the project.

README12pt70

README is present.

Contributing guide5pt97

Contributing guide is detailed and thorough.

License6pt100

Licensed under Apache-2.0.

Engineering

79

CI/CD14pt57

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

Tests18pt80

Test files detected (.mocharc.js).

Reproducibility6pt90

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

Linting and formatting5pt100

Linter or formatter configured (.eslintrc.json).

Issue and PR templates6pt100

Issue or PR templates present.

Project health

100

Dependency manifest6pt100

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

  • 9 / 35
    Commits (30d / 90d)
  • 1,818
    Forks
  • 128
    Releaseslatest 6y ago

Community

  • 75% - Good
    Community health
  • -
    authors own >50% of commits
  • 10,180
    Watchers

Responsiveness

  • -
    Median issue response
  • 3d 1h
    Median PR merge time
  • 35
    Open issues
Repository files35 root entries
  • .evergreen
  • .github
    Good: CI is configured (.github/workflows/build_and_commit_docs.yml).
    Good: Dependabot covers 3 ecosystems (gitsubmodule, github-actions, npm). Dependencies stay current.
    Good: Issue or PR templates present.
  • docs
  • etc
  • src
  • test
  • .dockerignore
  • .eslintignore
  • .eslintrc.json
    Good: Linter or formatter configured (.eslintrc.json).
  • .gitignore
    Good: .gitignore present.
  • .gitmodules
  • .mocharc.js
    Good: Test files detected (.mocharc.js).
  • .npmignore
  • .nycrc.json
  • .prettierrc.json
  • .release-please-manifest.json
  • AGENTS.md
  • api-extractor.json
  • CLAUDE.md
  • CODE_OF_CONDUCT.md
    Good: Code of conduct present.
  • CONTRIBUTING.md
    Good: Contributing guide is detailed and thorough.
    Good: Contributing guide includes setup/install instructions.
    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.
  • CONTRIBUTORS.md
  • drivers-evergreen-tools
  • global.d.ts
  • HISTORY.md
  • LICENSE.md
    Good: Licensed under Apache-2.0.
  • 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.
    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.
    Issue: No run or usage instructions found (−45 pts).Fix: Add a section showing how to start or use the project.
  • release-please-config.json
  • sbom.json
  • THIRD-PARTY-NOTICES
  • tsconfig.json
  • tsdoc.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/mongodb/node-mongodb-native)](https://www.repo-grade.com/report/mongodb/node-mongodb-native)

More graded TypeScript repos