Good community traction and solid fundamentals. Nearly in the top tier.
Strapi Documentation
Documentation
86
README is present.
Contributing guide is detailed and thorough.
README documents how to install the project.
Licensed under Other.
Engineering
47
No tests detected anywhere in the repository.
→ Add automated tests. They prove the code works and give contributors confidence to make changes.
CI is configured (.github/workflows/auto-label-prs-by-contributor-type.yml).
Lockfile present (docusaurus/scripts/redirects-utilities/redirection-analysis/yarn.lock). Installs are reproducible.
Linter or formatter configured (.editorconfig).
Issue or PR templates present.
Project health
100
Dependency manifest found (docusaurus/package.json).
Repository has a description.
Actively maintained (pushed within the last month).
.gitignore present.
Repository health signals
Activity, community, and responsiveness at scan time
Activity
- —Commits (30d / 90d)
- 1,262Forks
- 155Releaseslatest 3y ago
Community
- —Community health
- —authors own >50% of commits
- 1,278Watchers
Responsiveness
- 24hMedian issue response
- 3d 9hMedian PR merge time
- 36Open issues
Repository files21 root entries
- .claude-plugin
- .cursor
- .githubGood: CI is configured (.github/workflows/auto-label-prs-by-contributor-type.yml).Good: Issue or PR templates present.
- .vscode
- agents
- claude-plugins
- docusaurusGood: Lockfile present (docusaurus/scripts/redirects-utilities/redirection-analysis/yarn.lock). Installs are reproducible.Good: Dependency manifest found (docusaurus/package.json).
- .editorconfigGood: Linter or formatter configured (.editorconfig).
- .gitignoreGood: .gitignore present.
- .prettierignore
- .sclt-changelog.json
- 12-rules-of-technical-writing.md
- AGENTS.md
- CLAUDE.md
- CODE_OF_CONDUCT.mdGood: Code of conduct present.
- CONTRIBUTING.mdGood: 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
- LICENSEGood: Licensed under Other.
- README.mdGood: 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.mdGood: Security policy present.
- STYLE_GUIDE.pdf