Polished and well engineered. Punching above its star count.

Generates a .oxlintrc.json from an existing ESLint flat config.

Documentation

90

Contributing guide5pt52

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.

Install and run instructions9pt90

README documents how to install the project.

README12pt100

README is present.

License6pt100

Licensed under MIT.

Engineering

81

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.

Reproducibility6pt80

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

CI/CD14pt85

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

Tests18pt100

Test files detected (bin/config-loader.spec.ts).

Linting and formatting5pt100

Linter or formatter configured (devDependency in package.json).

Project health

98

Dependency manifest6pt93

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)
  • 12
    Forks
  • 93
    Releaseslatest 1y ago

Community

  • Community health
  • authors own >50% of commits
  • 181
    Watchers

Responsiveness

  • 14h
    Median issue response
  • <1h
    Median PR merge time
  • 19
    Open issues
Repository files21 root entries
  • .github
    Good: CI is configured (.github/workflows/build.yml).
  • .husky
  • .vscode
  • bin
    Good: Test files detected (bin/config-loader.spec.ts).
  • integration_test
  • scripts
  • src
  • .gitignore
    Good: .gitignore present.
  • .node-version
    Good: Environment pinned via .node-version.
  • .oxfmtrc.jsonc
  • .oxlintrc.json
  • .prettierignore
  • CONTRIBUTING.md
    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).
    Issue: Contributing guide lacks a PR workflow section (−8 pts).Fix: Explain how to fork, branch, and open a pull request so contributors know what to expect.
    Good: Contributing guide includes code examples.
  • 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.
    Good: README includes status badges.
    Good: README documents how to install the project.
    Good: README documents how to run the project.
  • tsconfig.json
  • tsdown.config.js
  • vitest.config.ts