remoteoss/json-schema-form

0

/ 100

Documentation76
Engineering98
Health84
JavaScript154MIT1d ago
Grade a repo

Polished and well engineered. Punching above its star count.

Documentation

76

Install and run instructions9pt45

README documents how to install the project.

README12pt80

README is present.

Contributing guide5pt92

Contributing guide is detailed and thorough.

License6pt100

Licensed under MIT.

Engineering

98

Reproducibility6pt80

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

Tests18pt100

Test files detected (jest.config.mjs).

CI/CD14pt100

CI is configured (.github/workflows/actions-v0.yml).

Linting and formatting5pt100

Linter or formatter configured (.prettierrc).

Issue and PR templates6pt100

Issue or PR templates present.

Project health

84

Repository metadata5pt40

No repository description set on GitHub (−60 pts).

→ Add a one-line description in the repo Settings → About. It appears in search results and social previews.

Dependency manifest6pt100

Dependency manifest found (package.json).

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)
  • 22
    Forks
  • 68
    Releaseslatest 2y ago

Community

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

Responsiveness

  • 3d
    Median issue response
  • 3d 12h
    Median PR merge time
  • 19
    Open issues
Repository files25 root entries
  • .github
    Good: CI is configured (.github/workflows/actions-v0.yml).
    Good: Issue or PR templates present.
  • .husky
  • .vscode
  • scripts
  • src
  • test
  • v0
  • .gitignore
    Good: .gitignore present.
  • .gitmodules
  • .nvmrc
    Good: Environment pinned via .nvmrc.
  • .prettierrc
    Good: Linter or formatter configured (.prettierrc).
  • babel.config.mjs
  • CHANGELOG.md
  • CONTRIBUTING.md
    Good: Contributing guide is detailed and thorough.
    Good: Contributing guide includes setup/install instructions.
    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.
    Good: Contributing guide includes code examples.
  • eslint.config.mjs
  • jest.config.mjs
    Good: Test files detected (jest.config.mjs).
  • json-schema-form.schema.json
  • json-schema-test-suite
  • LICENSE
    Good: Licensed under MIT.
  • MIGRATING.md
  • package.json
    Good: Dependency manifest found (package.json).
  • pnpm-lock.yaml
    Good: Lockfile present (pnpm-lock.yaml). Installs are reproducible.
  • 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.
    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.
    Issue: No run or usage instructions found (−45 pts).Fix: Add a section showing how to start or use the project.
  • tsconfig.json
  • tsup.config.js