Good shape overall. A few tweaks would push it into the top tier.

๐ŸŒ‰ Experience Nuxt 3 features on existing Nuxt 2 projects

Documentation

65

Contributing guide5pt0

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.

README12pt55

README is present.

Install and run instructions9pt90

README documents how to install the project.

License6pt100

Licensed under MIT.

Engineering

72

Tests18pt35

Test files detected (packages/bridge/test).

Reproducibility6pt70

Lockfile present (pnpm-lock.yaml). Installs are reproducible.

CI/CD14pt100

CI is configured (.github/workflows/ci.yml).

Linting and formatting5pt100

Linter or formatter configured (eslint.config.mjs).

Issue and PR templates6pt100

Issue or PR templates present.

Project health

92

Dependency manifest6pt75

Dependency manifest found (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
  • 13
    Releaseslatest 2y ago

Community

  • โ€”
    Community health
  • โ€”
    authors own >50% of commits
  • 287
    Watchers

Responsiveness

  • 11h
    Median issue response
  • 23h
    Median PR merge time
  • 127
    Open issues
Repository files19 root entries
  • .github
    Good: CI is configured (.github/workflows/ci.yml).
    Good: Issue or PR templates present.
  • packages
    Good: Test files detected (packages/bridge/test).
  • playground
  • scripts
  • test
  • .gitignore
    Good: .gitignore present.
  • .npmrc
  • CHANGELOG.md
  • CODEOWNERS
  • eslint.config.mjs
    Good: Linter or formatter configured (eslint.config.mjs).
  • knip.json
  • LICENSE
    Good: Licensed under MIT.
  • package.json
    Good: Dependency manifest found (package.json).
  • pnpm-lock.yaml
    Good: Lockfile present (pnpm-lock.yaml). Installs are reproducible.
  • pnpm-workspace.yaml
  • README.md
    Good: 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.
    Good: README documents how to run the project.
  • renovate.json
  • tsconfig.json
  • vitest.config.ts