tinacms/tina.io

0

/ 100

Documentation64
Engineering100
Health92
MDX299today
Grade a repo

Polished and well engineered. Punching above its star count.

Website for TinaCMS 🦙 - General info, documentation, blogs & contribution guidelines.

Documentation

64

License6pt0

No license detected.

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

Contributing guide5pt61

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.

README12pt70

README is present.

Install and run instructions9pt100

README documents how to install the project.

Engineering

100

Tests18pt100

Test files detected (components/PageMetadata/authorUtils.test.ts).

CI/CD14pt100

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

Linting and formatting5pt100

Linter or formatter configured (.editorconfig).

Reproducibility6pt100

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

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)
  • 1,507
    Forks
  • 0
    Releases

Community

  • 50% - Fair
    Community health
  • 6 bus factor
    authors own >50% of commits
  • 299
    Watchers

Responsiveness

  • 179d 5h
    Median issue response
  • <1h
    Median PR merge time
  • 245
    Open issues
Repository files49 root entries
  • _docs
  • .github
    Good: CI is configured (.github/workflows/nodejs.yml).
    Good: Dependabot covers 2 ecosystems (github-actions, npm). Dependencies stay current.
    Good: Issue or PR templates present.
  • .vscode
  • app
  • components
    Good: Test files detected (components/PageMetadata/authorUtils.test.ts).
  • content
  • data-api
  • docs
  • indices
  • lib
  • playwright-report
  • public
  • rss
  • scripts
  • src
  • styles
  • test-results
  • tests
  • tina
  • utils
  • .babelrc
  • .biomeignore
  • .editorconfig
    Good: Linter or formatter configured (.editorconfig).
  • .env.example
  • .gitignore
    Good: .gitignore present.
  • .lighthouserc.json
  • .nvmrc
    Good: Environment pinned via .nvmrc.
  • .vercelignore
  • .yarnrc.yml
  • AGENTS.md
  • biome.json
  • CLAUDE.md
  • components.json
  • 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.
    Issue: Contributing guide has no code examples (−5 pts).Fix: Add code blocks showing example commands for setup, running tests, and submitting a PR.
  • create.jest.config.js
  • custom.d.ts
  • jest.config.js
  • middleware.ts
  • next-env.d.ts
  • next-sitemap.config.js
  • next.config.js
  • package.json
    Good: Dependency manifest found (package.json).
  • playwright.config.ts
  • pnpm-lock.yaml
    Good: Lockfile present (pnpm-lock.yaml). Installs are reproducible.
  • postcss.config.js
  • 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.
    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.
  • tailwind.config.js
  • tsconfig.json
  • vercel.json