mongodb/mongo
Grade a repo

91

/ 100

GradeA

Excellent work. The main thing left to polish is a contributing guide.

Top 11% of 5,156 graded repos

The MongoDB Database

Documentation86
Engineering90
Health100
C++28,523Other19d ago

Top fixes

Highest-impact changes first, ranked by point weight

10 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
    README12pt

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

  3. 3
    Install and run instructions9pt

    Add a .env.example listing all required environment variables so contributors know what to set up.

  4. 4
    Reproducibility6pt

    Add .github/dependabot.yml with at least one package-ecosystem entry, or a renovate.json, so dependencies are updated automatically.

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

86

Contributing guide5pt52

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

This repository is large enough that GitHub truncated the file tree. The scan is based on a partial file list, so some checks may under-report.

Install and run instructions9pt90

README documents how to install the project.

License6pt100

Licensed under Other.

Engineering

90

Tests18pt80

Test files detected (.github/actions/pr-approval-recency/tests).

Reproducibility6pt80

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

CI/CD14pt100

CI is configured (src/third_party/cares/dist/appveyor.yml).

Linting and formatting5pt100

Linter or formatter configured (.editorconfig).

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

  • 709 / 3602
    Commits (30d / 90d)
  • 5,798
    Forks
  • 0
    Releases

Community

  • 62% - Fair
    Community health
  • 40 bus factor
    authors own >50% of commits
  • 28,523
    Watchers

Responsiveness

  • -
    Median issue response
  • 12h
    Median PR merge time
  • 32
    Open issues
Repository files51 root entries
  • .devcontainer
    Good: Environment pinned via .devcontainer/Dockerfile.
    Good: .gitignore present.
  • .github
    Good: Test files detected (.github/actions/pr-approval-recency/tests).
    Good: Issue or PR templates present.
  • .tmp
  • .vscode_defaults
  • bazel
    Good: Licensed under Other.
  • buildscripts
  • debian
  • distsrc
  • docs
  • etc
  • evergreen
  • jstests
  • modules_poc
  • rpm
  • src
    Good: Code of conduct present.
    Good: CI is configured (src/third_party/cares/dist/appveyor.yml).
    Good: Security policy present.
  • .bazelignore
  • .bazeliskrc
  • .bazelrc
  • .bazelrc.fuzztest
  • .bazelrc.local.example
  • .bazelrc.sync
  • .bazelrc.target_mongo_version
  • .bazelversion
  • .clang-format
  • .clang-tidy.in
  • .editorconfig
    Good: Linter or formatter configured (.editorconfig).
  • .gdbinit
  • .git-blame-ignore-revs
  • .gitattributes
  • .gitignore
  • .lldbinit
  • .mypy.ini
  • .npmrc
  • .prettierignore
  • .prettierrc
  • BUILD.bazel
  • CONTRIBUTING.rst
    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.
    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).
    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.
    Issue: Contributing guide has no code examples (−5 pts).Fix: Add code blocks showing example commands for setup, running tests, and submitting a PR.
  • CreativeCommons.txt
  • cspell.json
  • eslint.config.mjs
  • jsconfig.json
  • LICENSE-Community.txt
  • MODULE.bazel
  • MODULE.bazel.lock
  • OWNERS.yml
  • package.json
    Good: Dependency manifest found (package.json).
  • pnpm-lock.yaml
    Good: Lockfile present (pnpm-lock.yaml). Installs are reproducible.
  • pyproject.toml
  • 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.
  • README.third_party.md
  • sbom.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/mongo)](https://www.repo-grade.com/report/mongodb/mongo)

More graded C++ repos