55
/ 100
Getting some notice. Tests and CI would be the fastest wins.
Examples and code snippets demonstrating common ways of integrating Neon with various frameworks and languages.
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 C (77).
See your top fixesTop fixes
Highest-impact changes first, ranked by point weight
- 1Tests18pt
Wire your tests to a documented command (e.g. a test script in your build config) so the suite is reproducible.
- 2CI/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.
- 3README12pt
Expand with a description, install steps, usage, and examples.
- 4README12pt
Show a quick-start snippet so contributors can see what using your project looks like.
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
50
No license detected.
→ Add a LICENSE file. Without one, nobody can legally use, copy, or contribute to your code.
No install instructions found in the README (−45 pts).
→ Add a section showing how to install dependencies.
README is present.
Contributing guide is too short for full depth credit (−6 pts). 400+ words earns the full +12 pts.
→ Add setup instructions, code style notes, and how to run tests.
Engineering
41
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.
No dependency lockfile found (−70 pts).
→ Commit package-lock.json, pnpm-lock.yaml, yarn.lock, or bun.lock so Node installs are repeatable.
Test files detected (ai/fuzzy-semantic-search-nextjs/lib/normalize.test.ts).
Linter or formatter configured (ai/hybrid-search-nextjs/.eslintrc.json).
Project health
100
Dependency manifest found (ai/fuzzy-semantic-search-nextjs/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)
- 33Forks
- 0Releases
Community
- 50% - FairCommunity health
- 3 bus factorauthors own >50% of commits
- 76Watchers
Responsiveness
- 4d 22hMedian issue response
- 4d 8hMedian PR merge time
- 45Open issues
Repository files25 root entries
- aiGood: Test files detected (ai/fuzzy-semantic-search-nextjs/lib/normalize.test.ts).Good: Linter or formatter configured (ai/hybrid-search-nextjs/.eslintrc.json).Good: Dependency manifest found (ai/fuzzy-semantic-search-nextjs/package.json).
- assets
- auth
- elements_data_set
- neon-getting-started
- with-ai-sdk
- with-encore
- with-files-sdk
- with-hono
- with-hyperdrive
- with-mastra
- with-mcp
- with-neon-serverless
- with-nextjs-drizzle-local-vercelGood: Environment pinned via with-nextjs-drizzle-local-vercel/docker-compose.yml.
- with-nodejs-pg-notify
- with-realtime-chat
- with-realtime-sse
- with-sveltekit-feature-flags
- with-tanstack-start-server-functions
- with-tanstack-start-static-server-functions
- .gitignoreGood: .gitignore present.
- bootstrap.yaml
- CONTRIBUTING.mdIssue: Contributing guide is too short for full depth credit (−6 pts). 400+ words earns the full +12 pts.Fix: Add setup instructions, code style notes, and how to run tests.Issue: Contributing guide lacks a setup section (−12 pts).Fix: Show new contributors how to get a local dev environment running.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.
- 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.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.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.
- vercel.json
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/neondatabase/examples)