Good shape overall. A few tweaks would push it into the top tier.
A comprehensive list of all free email domain providers.
Documentation
70
No CONTRIBUTING.md found (−47 pts base + up to −53 pts more for content).
→ Add a CONTRIBUTING.md telling newcomers how to get involved. Include setup, code style, test, and PR instructions.
README is present.
README documents how to install the project.
Licensed under MIT.
Engineering
74
No issue or PR templates found (−100 pts).
→ Add .github/ISSUE_TEMPLATE/ with bug_report.md and feature_request.md to guide contributors. It dramatically improves issue quality.
No dependency lockfile found (−70 pts).
→ Commit package-lock.json, pnpm-lock.yaml, yarn.lock, or bun.lock so Node installs are repeatable.
CI is configured (.github/workflows/main.yml).
Test files detected (test).
Linter or formatter configured (.editorconfig).
Project health
97
Dependency manifest found (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)
- 34Forks
- 119Releaseslatest 5y ago
Community
- —Community health
- —authors own >50% of commits
- 232Watchers
Responsiveness
- 3hMedian issue response
- <1hMedian PR merge time
- 0Open issues
Repository files14 root entries
- .githubGood: CI is configured (.github/workflows/main.yml).Good: Dependabot covers 2 ecosystems (npm, github-actions). Dependencies stay current.
- scripts
- testGood: Test files detected (test).
- .editorconfigGood: Linter or formatter configured (.editorconfig).
- .gitattributes
- .gitignoreGood: .gitignore present.
- .npmrc
- CHANGELOG.md
- domains.js
- domains.json
- index.d.ts
- LICENSE.mdGood: Licensed under MIT.
- package.jsonGood: Dependency manifest found (package.json).
- README.mdGood: README is present.Issue: README is fairly short (−10 pts). At 400+ chars you get partial credit; 1,500+ earns the full +20 pts.Fix: Expand with a description, install steps, usage, and examples.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.Good: README includes status badges.Good: README documents how to install the project.Good: README documents how to run the project.