tsz-org/tsz

0

/ 100

Documentation92
Engineering91
Health100
Rust512Apache-2.01d ago
Grade a repo

Polished and well engineered. Punching above its star count.

A performance-first TypeScript checker

Documentation

92

README12pt90

README is present.

Install and run instructions9pt90

README documents how to install the project.

Contributing guide5pt92

Contributing guide is detailed and thorough.

License6pt100

Licensed under Apache-2.0.

Engineering

91

CI/CD14pt72

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

Reproducibility6pt92

Lockfile present (Cargo.lock). Installs are reproducible.

Tests18pt100

Test files detected (crates/conformance/tests).

Linting and formatting5pt100

Rust linting configured (cargo clippy in CI).

Issue and PR templates6pt100

Issue or PR templates present.

Project health

100

Dependency manifest6pt100

Dependency manifest found (Cargo.toml).

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)
  • 11
    Forks
  • 24
    Releaseslatest 17d ago

Community

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

Responsiveness

  • <1h
    Median issue response
  • <1h
    Median PR merge time
  • 45
    Open issues
Repository files18 root entries
  • .agents
  • .cargo
  • .claude
  • .codex
  • .config
  • .github
    Good: CI is configured (.github/workflows/ci-health.yml).
    Good: Dependabot configured for github-actions.
    Good: Issue or PR templates present.
  • .vscode
  • crates
    Good: Test files detected (crates/conformance/tests).
  • docs
    Good: Contributing guide is detailed and thorough.
    Good: Contributing guide includes setup/install instructions.
    Good: Contributing guide describes code style expectations.
    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.
    Good: Contributing guide includes code examples.
  • scripts
    Good: Environment pinned via scripts/infra/cloud-run-gh-runner/Dockerfile.
  • .gitignore
    Good: .gitignore present.
  • .gitmodules
  • AGENTS.md
  • Cargo.lock
    Good: Lockfile present (Cargo.lock). Installs are reproducible.
  • Cargo.toml
    Good: Dependency manifest found (Cargo.toml).
  • deny.toml
  • LICENSE.txt
    Good: Licensed under Apache-2.0.
  • 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.
    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.