morluto/rea
Grade a repo

0

/ 100

GradeA

Exemplary work. Strong across project hygiene, documentation, and engineering.

Top 6% of 5,156 graded repos

Reverse engineer anything with agents, from app behavior down to native binaries.

Documentation94
Engineering93
Health100
TypeScript342,708MIT8d 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
    CI/CD14pt

    Add a lint step to catch style issues automatically.

  2. 2
    CI/CD14pt

    Add `tsc --noEmit`, `mypy`, or `cargo check` to catch type errors before they merge.

  3. 3
    CI/CD14pt

    Upload coverage to Codecov, Coveralls, or report it with `--coverage` flags.

  4. 4
    Install and run instructions9pt

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

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

94

Contributing guide5pt80

Contributing guide is detailed and thorough.

Install and run instructions9pt90

README documents how to install the project.

README12pt100

README is present.

License6pt100

Licensed under MIT.

Engineering

93

Reproducibility6pt80

Lockfile present (package-lock.json). Installs are reproducible.

CI/CD14pt85

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

Tests18pt100

Test files detected (bridge/mitmproxy/test_capture.py).

Linting and formatting5pt100

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

Issue and PR templates6pt100

Issue or PR templates present.

Project health

100

Dependency manifest6pt100

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

  • 2913 / 2973
    Commits (30d / 90d)
  • 86,433
    Forks
  • 38
    Releaseslatest 3mo ago

Community

  • 85% - Good
    Community health
  • 2 bus factor
    authors own >50% of commits
  • 342,708
    Watchers

Responsiveness

  • 4d 23h
    Median issue response
  • <1h
    Median PR merge time
  • 1,382
    Open issues
Repository files46 root entries
  • .agents
  • .github
    Good: CI is configured (.github/workflows/ci-full-pr.yml).
    Good: Issue or PR templates present.
  • .husky
  • bridge
    Good: Test files detected (bridge/mitmproxy/test_capture.py).
  • docs
  • experiments
  • licenses
  • native
  • scripts
  • src
  • tests
  • third_party
  • website
  • .gitattributes
  • .gitignore
    Good: .gitignore present.
  • .gitmodules
  • .jscpd.json
  • .npmrc
  • .nvmrc
    Good: Environment pinned via .nvmrc.
  • .oxfmtrc.json
  • .oxlintrc.json
  • .release-please-manifest.json
  • AGENTS.md
  • CHANGELOG.md
  • CONTRIBUTING.md
    Good: Contributing guide is detailed and thorough.
    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.
    Good: Contributing guide explains how to run tests.
    Good: Contributing guide describes the PR/review workflow.
    Good: Contributing guide includes code examples.
  • DISCLAIMER.md
  • install.sh
  • knip.json
  • LICENSE
    Good: Licensed under MIT.
  • package-lock.json
    Good: Lockfile present (package-lock.json). Installs are reproducible.
  • package.json
    Good: Dependency manifest found (package.json).
  • 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.
  • release-please-config.json
  • SECURITY.md
    Good: Security policy present.
  • server.json
  • stryker.config.mjs
  • stryker.semantics.config.mjs
  • THIRD_PARTY_NOTICES.md
  • tsconfig.build.json
  • tsconfig.frida-verification.json
  • tsconfig.json
  • tsconfig.reverse-tools-mutation.json
  • turbo.json
  • vitest.config.ts
  • vitest.reverse-tools-semantics.config.ts
  • vitest.reverse-tools.config.ts
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/morluto/rea)](https://www.repo-grade.com/report/morluto/rea)

More graded TypeScript repos