strapi/documentation
Grade a repo

70

/ 100

GradeC

Good community traction and solid fundamentals. Nearly in the top tier.

Top 46% of 5,156 graded repos

Strapi Documentation

Documentation86
Engineering47
Health100
JavaScript1,278Other1mo ago

Top fixes

Highest-impact changes first, ranked by point weight

12 to address
  1. 1
    Tests18pt

    Add automated tests. They prove the code works and give contributors confidence to make changes.

  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

86

README12pt75

README is present.

Contributing guide5pt89

Contributing guide is detailed and thorough.

Install and run instructions9pt90

README documents how to install the project.

License6pt100

Licensed under Other.

Engineering

47

Tests18pt0

No tests detected anywhere in the repository.

→ Add automated tests. They prove the code works and give contributors confidence to make changes.

CI/CD14pt57

CI is configured (.github/workflows/auto-label-prs-by-contributor-type.yml).

Reproducibility6pt70

Lockfile present (docusaurus/scripts/redirects-utilities/redirection-analysis/yarn.lock). Installs are reproducible.

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 (docusaurus/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

  • 107 / 325
    Commits (30d / 90d)
  • 1,262
    Forks
  • 155
    Releaseslatest 3y ago

Community

  • 100% - Good
    Community health
  • 1 bus factorlow
    author own >50% of commits
  • 1,278
    Watchers

Responsiveness

  • 24h
    Median issue response
  • 3d 9h
    Median PR merge time
  • 34
    Open issues
Repository files21 root entries
  • .claude-plugin
  • .cursor
  • .github
    Good: CI is configured (.github/workflows/auto-label-prs-by-contributor-type.yml).
    Good: Issue or PR templates present.
  • .vscode
  • agents
  • claude-plugins
  • docusaurus
    Good: Lockfile present (docusaurus/scripts/redirects-utilities/redirection-analysis/yarn.lock). Installs are reproducible.
    Good: Dependency manifest found (docusaurus/package.json).
  • .editorconfig
    Good: Linter or formatter configured (.editorconfig).
  • .gitignore
    Good: .gitignore present.
  • .prettierignore
  • .sclt-changelog.json
  • 12-rules-of-technical-writing.md
  • AGENTS.md
  • 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.
    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).
    Good: Contributing guide describes the PR/review workflow.
    Good: Contributing guide includes code examples.
  • git-rules.md
  • LICENSE
    Good: Licensed under Other.
  • README.md
    Good: README is present.
    Good: README is well structured with multiple sections.
    Good: README includes screenshots or visuals. Great for first impressions.
    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.
  • SECURITY.md
    Good: Security policy present.
  • STYLE_GUIDE.pdf
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/strapi/documentation)](https://www.repo-grade.com/report/strapi/documentation)

More graded JavaScript repos