robotostudio/turbo-start-sanity
Grade a repo

0

/ 100

GradeC

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

Sanity + Next.js page-builder template

Documentation90
Engineering66
Health89
JavaScript167MITtoday

Documentation

90

Contributing guide5pt60

CONTRIBUTING guide is very brief (−12 pts for depth). 150+ words earns +6 pts; 400+ earns +12 pts.

→ Add setup instructions, code style notes, and how to run tests.

README12pt90

README is present.

Install and run instructions9pt100

README documents how to install the project.

License6pt100

Licensed under MIT.

Engineering

66

Tests18pt35

Test files detected (apps/web/tests).

CI/CD14pt72

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

Reproducibility6pt82

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

Linting and formatting5pt100

Linter or formatter configured (biome.jsonc).

Issue and PR templates6pt100

Issue or PR templates present.

Project health

89

Dependency manifest6pt65

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)
  • 57
    Forks
  • 1
    Releaseslatest 1mo ago

Community

  • -
    Community health
  • -
    authors own >50% of commits
  • 167
    Watchers

Responsiveness

  • 1d 1h
    Median issue response
  • <1h
    Median PR merge time
  • 13
    Open issues
Repository files27 root entries
  • .agents
    Issue: CONTRIBUTING guide is very brief (−12 pts for depth). 150+ words earns +6 pts; 400+ earns +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.
    Issue: Contributing guide has no code examples (−5 pts).Fix: Add code blocks showing example commands for setup, running tests, and submitting a PR.
  • .claude
  • .cursor
  • .github
    Good: CI is configured (.github/workflows/ci.yml).
    Good: Dependabot configured for npm.
    Good: Issue or PR templates present.
  • .vscode
  • apps
    Good: Test files detected (apps/web/tests).
  • github
  • packages
  • .gitignore
    Good: .gitignore present.
  • .npmrc
  • biome.jsonc
    Good: Linter or formatter configured (biome.jsonc).
  • CLAUDE.md
  • CODE_OF_CONDUCT.md
    Good: Code of conduct present.
  • CONTRIBUTING.md
  • engine-divider.png
  • 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.
    Good: README includes screenshots or visuals. Great for first impressions.
    Good: README has code examples.
    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.
  • SECURITY.md
    Good: Security policy present.
  • skills-lock.json
  • sonar-project.properties
  • tasteful-safe-option-og.png
  • tsconfig.json
  • turbo-start-sanity-og.png
  • turbo.json