62
/ 100
Getting some notice. Tests and CI would be the fastest wins.
Apache Zeppelin Extension for VS Code
A low grade is a to-do list, not a judgment of your code
Most gaps here are documentation, tests, and setup, not the code itself. Closing your top 3 gaps alone would lift this repo to B (86).
See your top fixesTop fixes
Highest-impact changes first, ranked by point weight
- 1CI/CD14pt
If your CI lives elsewhere (a private repo that builds this one) or this project is itself a CI/CD tool, mark this check Not Applicable. Otherwise add a GitHub Actions workflow that runs tests on each push. It takes 15 minutes and reassures contributors their changes won't break things.
- 2README12pt
Add a GIF, screenshot, or logo image. It is the fastest way to show what your project does.
- 3README12pt
Show a quick-start snippet so contributors can see what using your project looks like.
- 4README12pt
Add CI/build status badges from shields.io or your CI provider to signal project health.
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
52
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
56
No CI configuration detected in this repository.
→ If your CI lives elsewhere (a private repo that builds this one) or this project is itself a CI/CD tool, mark this check Not Applicable. Otherwise add a GitHub Actions workflow that runs tests on each push. It takes 15 minutes and reassures contributors their changes won't break things.
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.
Lockfile present (package-lock.json). Installs are reproducible.
Test files detected (src/test).
Linter or formatter configured (.eslintrc.json).
Project health
95
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)
- 4Forks
- 28Releaseslatest 2y ago
Community
- 42% - WeakCommunity health
- 1 bus factorlowauthor own >50% of commits
- 17Watchers
Responsiveness
- 8hMedian issue response
- <1hMedian PR merge time
- 3Open issues
Repository files16 root entries
- .vscode
- srcGood: Test files detected (src/test).
- .eslintrc.jsonGood: Linter or formatter configured (.eslintrc.json).
- .gitignoreGood: .gitignore present.
- .vscodeignore
- CHANGELOG.md
- LICENSEGood: Licensed under MIT.
- package-lock.jsonGood: Lockfile present (package-lock.json). Installs are reproducible.
- package.jsonGood: Dependency manifest found (package.json).
- README.mdGood: README is present.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.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.Issue: No run or usage instructions found (−45 pts).Fix: Add a section showing how to start or use the project.
- tsconfig.base.json
- tsconfig.json
- vitest.config.ts
- webpack.config.js
- zeppelin-notebook.ico
- zeppelin.png
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/allen-li1231/zeppelin-vscode)