Getting some notice. Tests and CI would be the fastest wins.
A Discord application to call your cellphone through Twilio in case of emergencies. Built with Cloudflare Workers
Documentation
66
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.
No install instructions found in the README (−45 pts).
→ Add a section showing how to install dependencies.
README is present.
Licensed under MIT.
Engineering
41
No tests detected anywhere in the repository.
→ Add automated tests. They prove the code works and give contributors confidence to make changes.
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.
CI is configured (.github/workflows/linting.yml).
Lockfile present (pnpm-lock.yaml). Installs are reproducible.
Linter or formatter configured (eslint.config.mjs).
Project health
89
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)
- 9Forks
- 0Releases
Community
- —Community health
- —authors own >50% of commits
- 47Watchers
Responsiveness
- 42d 19hMedian issue response
- <1hMedian PR merge time
- 10Open issues
Repository files14 root entries
- .githubGood: Code of conduct present.Good: CI is configured (.github/workflows/linting.yml).
- src
- .gitattributes
- .gitignoreGood: .gitignore present.
- .npmrc
- .nvmrcGood: Environment pinned via .nvmrc.
- eslint.config.mjsGood: Linter or formatter configured (eslint.config.mjs).
- LICENSEGood: Licensed under MIT.
- package.jsonGood: Dependency manifest found (package.json).
- pnpm-lock.yamlGood: Lockfile present (pnpm-lock.yaml). Installs are reproducible.
- pnpm-workspace.yaml
- README.mdGood: 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.Issue: No install instructions found in the README (−45 pts).Fix: Add a section showing how to install dependencies.Good: README documents how to run the project.
- tsconfig.json
- wrangler.toml