perryts/perry
Grade a repo

95

/ 100

GradeA

A well-known project done right. Strong docs and solid engineering throughout.

Top 6% of 5,156 graded repos

A native TypeScript compiler written in Rust. Compiles TypeScript directly to executables using SWC and LLVM.

Documentation97
Engineering100
Health79
Rust3,865MIT1mo ago

Outstanding. A score of 95/100 puts this repo in a very small tier of truly well-engineered projects.

Top fixes

Highest-impact changes first, ranked by point weight

8 to address
  1. 1
    Install and run instructions9pt

    Add a .env.example listing all required environment variables so contributors know what to set up.

  2. 2
    Dependency manifest6pt

    Add a one-line description to package.json. It appears in npm search and on GitHub.

  3. 3
    Dependency manifest6pt

    Add a `repository` field pointing to the GitHub URL so npm knows where the source lives.

  4. 4
    Dependency manifest6pt

    Add a `keywords` array to help people find your package on npm.

Working through the fixes? Let every push regrade itself.

The free GitHub App rescans this repo on every push and posts the grade as a commit check, so the score climbs without coming back to rescan by hand.

Install the GitHub App

Scorecard

Every check, grouped by category and sorted worst-first

Documentation

97

Install and run instructions9pt90

README documents how to install the project.

Contributing guide5pt97

Contributing guide is detailed and thorough.

README12pt100

README is present.

License6pt100

Licensed under MIT.

Engineering

100

Tests18pt100

Test files detected (crates/perry-api-manifest/tests).

CI/CD14pt100

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

Linting and formatting5pt100

Linter or formatter configured (rustfmt.toml).

Reproducibility6pt100

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

Issue and PR templates6pt100

Issue or PR templates present.

Project health

79

Dependency manifest6pt55

Dependency manifest found (Cargo.toml).

Housekeeping3pt60

.gitignore present.

Repository metadata5pt100

Repository has a description.

Activity5pt100

Actively maintained (pushed within the last month).

Repository health signals

Activity, community, and responsiveness at scan time

Activity

  • -
    Commits (30d / 90d)
  • 133
    Forks
  • 157
    Releaseslatest 4mo ago

Community

  • 75% - Good
    Community health
  • -
    authors own >50% of commits
  • 3,865
    Watchers

Responsiveness

  • 2h
    Median issue response
  • 5h
    Median PR merge time
  • 55
    Open issues
Repository files60 root entries
  • .claude
  • .githooks
  • .github
    Good: CI is configured (.github/workflows/test.yml).
    Good: Dependabot covers 2 ecosystems (cargo, github-actions). Dependencies stay current.
    Good: Issue or PR templates present.
  • android-build
  • benchmarks
    Issue: Build artifacts or local files may be committed (benchmarks/compiler_output/fixtures/native_memory_fixture_project/node_modules/@perry-fixtures) (−40 pts).Fix: Remove them and add to .gitignore.
  • bucket
  • crates
    Good: Test files detected (crates/perry-api-manifest/tests).
  • docs
    Good: Security policy present.
  • example-code
  • examples
  • npm
  • packages
  • packaging
  • res
  • scripts
  • src
  • target
  • templates
  • test-compat
  • test-coverage
  • test-features
  • test-files
  • test-parity
  • tests
  • types
  • winget-manifests
  • .dockerignore
  • .git-blame-ignore-revs
  • .gitignore
    Good: .gitignore present.
  • Cargo.lock
    Good: Lockfile present (Cargo.lock). Installs are reproducible.
  • Cargo.toml
    Good: Dependency manifest found (Cargo.toml).
  • CHANGELOG.md
  • CLAUDE.md
  • clusterAg
  • CNAME
  • CODE_OF_CONDUCT.md
    Good: Code of conduct present.
  • 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.
  • docker-compose.yml
  • Dockerfile
    Good: Environment pinned via Dockerfile.
  • Dockerfile.dev
  • isoA
  • LICENSE
    Good: Licensed under MIT.
  • llms.txt
  • m
  • m5
  • NM_DEVIRT_PLAN.md
  • package-lock.json
  • package.json
  • parity_status.sh
  • PERF_RUN_LOG.md
  • 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.
  • run_llvm_sweep.sh
  • run_module_parity.sh
  • run_parity_tests.sh
  • run_tests.sh
  • rustfmt.toml
    Good: Linter or formatter configured (rustfmt.toml).
  • TYPE_LOWERING_GUIDANCE.md
  • TYPE_LOWERING.md
  • W6_ISSUE_DRAFT.md
  • wasm_ui_demo.html
RepoGrade badge preview

Add this badge to your README

It updates automatically each time the repo is re-graded.

[![RepoGrade](https://www.repo-grade.com/api/badge/perryts/perry)](https://www.repo-grade.com/report/perryts/perry)

More graded Rust repos