fryuni/inox-tools

0

/ 100

Documentation43
Engineering80
Health91
TypeScript141MIT1d ago
Grade a repo

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

Oxygen-free tools for Astronauts.

Documentation

43

Contributing guide5pt5

No CONTRIBUTING.md found (−47 pts base + up to −53 pts more for content).

→ Add a CONTRIBUTING.md telling newcomers how to get involved. Include setup, code style, test, and PR instructions.

README12pt30

README is present.

Install and run instructions9pt45

No install instructions found in the README (−45 pts).

→ Add a section showing how to install dependencies.

License6pt100

Licensed under MIT.

Engineering

80

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 (pnpm-lock.yaml). Installs are reproducible.

CI/CD14pt85

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

Tests18pt100

Test files detected (packages/astro-when/tests).

Linting and formatting5pt100

Linter or formatter configured (packages/inline-mod/.eslintrc.cjs).

Project health

91

Dependency manifest6pt73

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)
  • 13
    Forks
  • 384
    Releaseslatest 2y ago

Community

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

Responsiveness

  • 2h
    Median issue response
  • <1h
    Median PR merge time
  • 10
    Open issues
Repository files27 root entries
  • .changeset
  • .github
    Good: CI is configured (.github/workflows/ci.yml).
  • .husky
  • .memory
  • assets
  • docs
  • examples
  • packages
    Good: Test files detected (packages/astro-when/tests).
    Good: Linter or formatter configured (packages/inline-mod/.eslintrc.cjs).
  • patches
  • scripts
  • turbo
  • .envrc
  • .gitignore
    Good: .gitignore present.
  • .prettierignore
  • .prototools
  • AGENTS.md
  • CODE_OF_CONDUCT.md
    Good: Code of conduct present.
  • flake.lock
  • flake.nix
  • 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
  • prettier.config.js
  • 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.
    Issue: README has little structure (−15 pts). Add 2-3 headings for +8 pts; 4+ earns +15 pts.Fix: Break it into sections (Overview, Install, Usage, Contributing) using Markdown headings.
    Good: README includes screenshots or visuals. Great for first impressions.
    Issue: README has no code examples (−15 pts).Fix: Show a quick-start snippet so contributors can see what using your project looks like.
    Issue: No live demo link in the README (−20 pts).Fix: Link to a deployed version, docs site, or demo video. Users want to see it running.
    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.
    Issue: No install instructions found in the README (−45 pts).Fix: Add a section showing how to install dependencies.
    Good: README documents how to run the project.
  • tsconfig.base.json
  • turbo.json