0
/ 100
Polished and well engineered. Punching above its star count.
Another Telegram RSS bot but in Node.js Telegram RSS 机器人
Top fixes
Highest-impact changes first, ranked by point weight
- 1README12pt
Show a quick-start snippet so contributors can see what using your project looks like.
- 2Install and run instructions9pt
Add a section showing how to start or use the project.
- 3Install and run instructions9pt
Add a .env.example listing all required environment variables so contributors know what to set up.
- 4Reproducibility6pt
Add additional package-ecosystem entries (especially github-actions) to keep all dependencies current.
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.
Scorecard
Every check, grouped by category and sorted worst-first
Documentation
63
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 documents how to install the project.
README is present.
Licensed under MIT.
Engineering
99
Lockfile present (package-lock.json). Installs are reproducible.
Test files detected (test).
CI is configured (.github/workflows/test-docker.yml).
Linter or formatter configured (.prettierrc).
Issue or PR templates present.
Project health
100
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)
- 91Forks
- 35Releaseslatest 7y ago
Community
- -Community health
- -authors own >50% of commits
- 405Watchers
Responsiveness
- 5hMedian issue response
- 6hMedian PR merge time
- 17Open issues
Repository files27 root entries
- .devcontainer
- .githubGood: CI is configured (.github/workflows/test-docker.yml).Good: Dependabot configured for npm.Good: Issue or PR templates present.
- .vscode
- data
- i18n
- logs
- source
- testGood: Test files detected (test).
- tools
- _typos.toml
- .dockerignore
- .gitignoreGood: .gitignore present.
- .node-version
- .nvmrc
- .prettierignore
- .prettierrcGood: Linter or formatter configured (.prettierrc).
- app.json
- CHANGELOG.md
- DockerfileGood: Environment pinned via Dockerfile.
- eslint.config.mjs
- LICENSEGood: Licensed under MIT.
- package-lock.jsonGood: Lockfile present (package-lock.json). Installs are reproducible.
- package.jsonGood: Dependency manifest found (package.json).
- Procfile
- 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.Good: README includes status badges.Good: README documents how to install the project.Issue: No run or usage instructions found (−45 pts).Fix: Add a section showing how to start or use the project.
- tsconfig.json
- tsconfig.test.json
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/fengkx/noderssbot)