rvermootenct/zod

0

/ 100

Documentation93
Engineering84
Health64
0MIT3y ago
Grade a repo

Solid engineering. The main gap is visibility.

TypeScript-first schema validation with static type inference

Documentation

93

Contributing guide5pt74

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.

Install and run instructions9pt90

README documents how to install the project.

README12pt100

README is present.

License6pt100

Licensed under MIT.

Engineering

84

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.

Reproducibility6pt70

Lockfile present (bun.lockb). Installs are reproducible.

Tests18pt100

Test files detected (deno/lib/__tests__).

CI/CD14pt100

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

Linting and formatting5pt100

Linter or formatter configured (.editorconfig).

Project health

64

Activity5pt5

No pushes in over 2 years. Looks unmaintained (−95 pts).

→ A recent commit signals the project is alive and worth using.

Repository metadata5pt60

Repository has a description.

Dependency manifest6pt100

Dependency manifest found (package.json).

Housekeeping3pt100

.gitignore present.

Repository health signals

Activity, community, and responsiveness at scan time

Activity

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

Community

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

Responsiveness

  • —
    Median issue response
  • —
    Median PR merge time
  • 0
    Open issues
Repository files38 root entries
  • .github
    Good: CI is configured (.github/workflows/test.yml).
  • .husky
  • deno
    Good: Test files detected (deno/lib/__tests__).
  • src
  • static
  • _redirects
  • .dependency-cruiser.js
  • .editorconfig
    Good: Linter or formatter configured (.editorconfig).
  • .eslintignore
  • .eslintrc.js
  • .gitignore
    Good: .gitignore present.
  • .nojekyll
  • .prettierrc.yaml
  • bun.lockb
    Good: Lockfile present (bun.lockb). Installs are reproducible.
  • CHANGELOG.md
  • CODE_OF_CONDUCT.md
    Good: Code of conduct present.
  • 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.
    Good: Contributing guide explains how to run tests.
    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.
  • ERROR_HANDLING.md
  • FUNDING.yml
  • index.d.ts
  • index.html
  • jest.config.json
  • LICENSE
    Good: Licensed under MIT.
  • logo.svg
  • MIGRATION.md
  • package.json
    Good: Dependency manifest found (package.json).
  • playground.ts
  • README_ZH.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.
    Good: README includes status badges.
    Good: README documents how to install the project.
    Good: README documents how to run the project.
  • README.md
  • robots.txt
  • rollup.config.js
  • tsconfig.base.json
  • tsconfig.cjs.json
  • tsconfig.esm.json
  • tsconfig.json
  • tsconfig.test.json
  • tsconfig.types.json
  • yarn.lock