neondatabase/examples

0

/ 100

Documentation50
Engineering41
Health100
TypeScript751d ago
Grade a repo

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.

Documentation

50

License6pt0

No license detected.

→ Add a LICENSE file. Without one, nobody can legally use, copy, or contribute to your code.

Install and run instructions9pt55

No install instructions found in the README (−45 pts).

→ Add a section showing how to install dependencies.

README12pt65

README is present.

Contributing guide5pt66

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

CI/CD14pt0

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.

Issue and PR templates6pt0

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.

Reproducibility6pt10

No dependency lockfile found (−70 pts).

→ Commit package-lock.json, pnpm-lock.yaml, yarn.lock, or bun.lock so Node installs are repeatable.

Tests18pt80

Test files detected (ai/fuzzy-semantic-search-nextjs/lib/normalize.test.ts).

Linting and formatting5pt100

Linter or formatter configured (ai/hybrid-search-nextjs/.eslintrc.json).

Project health

100

Dependency manifest6pt100

Dependency manifest found (ai/fuzzy-semantic-search-nextjs/package.json).

Repository metadata5pt100

Repository has a description.

Activity5pt100

Actively maintained (pushed within the last month).

Housekeeping3pt100

.gitignore present.

Repository health signals

Activity, community, and responsiveness at scan time

Activity

  • —
    Commits (30d / 90d)
  • 33
    Forks
  • 0
    Releases

Community

  • —
    Community health
  • —
    authors own >50% of commits
  • 75
    Watchers

Responsiveness

  • 4d 22h
    Median issue response
  • 4d 8h
    Median PR merge time
  • 45
    Open issues
Repository files25 root entries
  • ai
    Good: 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-vercel
    Good: 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
  • .gitignore
    Good: .gitignore present.
  • bootstrap.yaml
  • CONTRIBUTING.md
    Issue: 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.md
    Good: 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