mdn/fred
Grade a repo

93

/ 100

GradeA

Polished and well engineered. Punching above its star count.

Top 8% of 5,156 graded repos

MDN's frontend since late 2025, built with Web Components, Lit, and SSR for a fast, clean documentation experience. Fred = /fr(ont)e(n)d/.

Documentation84
Engineering100
Health92
JavaScript222MPL-2.01mo ago

Top fixes

Highest-impact changes first, ranked by point weight

8 to address
  1. 1
    README12pt

    Add a GIF, screenshot, or logo image. It is the fastest way to show what your project does.

  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
    Dependency manifest6pt

    Add a one-line description to package.json. It appears in npm search and on GitHub.

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

84

README12pt70

README is present.

Contributing guide5pt85

Contributing guide is detailed and thorough.

Install and run instructions9pt90

README documents how to install the project.

License6pt100

Licensed under MPL-2.0.

Engineering

100

Tests18pt100

Test files detected (test).

CI/CD14pt100

CI is configured (.github/workflows/main-review-companion.yml).

Linting and formatting5pt100

Linter or formatter configured (.editorconfig).

Reproducibility6pt100

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

Issue and PR templates6pt100

Issue or PR templates present.

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

  • -
    Commits (30d / 90d)
  • 51
    Forks
  • 46
    Releaseslatest 11mo ago

Community

  • 100% - Good
    Community health
  • -
    authors own >50% of commits
  • 222
    Watchers

Responsiveness

  • 5d 21h
    Median issue response
  • <1h
    Median PR merge time
  • 127
    Open issues
Repository files43 root entries
  • .github
    Good: CI is configured (.github/workflows/main-review-companion.yml).
    Good: Dependabot covers 2 ecosystems (npm, github-actions). Dependencies stay current.
    Good: Issue or PR templates present.
  • .vscode
  • build
  • components
  • hooks
  • l10n
  • legacy
  • public
  • scripts
  • symmetric-context
  • test
    Good: Test files detected (test).
  • types
  • utils
  • vendor
  • .editorconfig
    Good: Linter or formatter configured (.editorconfig).
  • .env-dist
  • .gitignore
    Good: .gitignore present.
  • .lefthook.yml
  • .npmignore
  • .npmrc
  • .nvmrc
    Good: Environment pinned via .nvmrc.
  • .prettierignore
  • .stylelintignore
  • build.sh
  • CHANGELOG.md
  • CODE_OF_CONDUCT.md
    Good: Code of conduct present.
  • CONTRIBUTING.md
    Good: Contributing guide is detailed and thorough.
    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.
    Good: Contributing guide describes the PR/review workflow.
    Good: Contributing guide includes code examples.
  • entry.client.js
  • entry.inline.js
  • entry.ssr.js
  • eslint.config.js
  • LICENSE
    Good: Licensed under MPL-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.
    Good: README documents how to run the project.
  • rspack.config.js
  • SECURITY.md
    Good: Security policy present.
  • server.js
  • stylelint.config.js
  • svgo.config.js
  • template.html
  • tsconfig.json
  • wdio.conf.js
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/mdn/fred)](https://www.repo-grade.com/report/mdn/fred)

More graded JavaScript repos