lloydrichards/stack-effect
Grade a repo

0

/ 100

GradeA

Well engineered for its size. A portfolio piece worth showing off.

Top 12% of 5,156 graded repos

Scaffolding CLI for full-stack TypeScript apps built on Effect. Quickly setup an Effect-first monorepo with best practices and a curated set of modules for common features like API servers, clients, databases, and more.

Documentation80
Engineering96
Health89
TypeScript13MIT1mo ago

Top fixes

Highest-impact changes first, ranked by point weight

14 to address
  1. 1
    README12pt

    Link to a deployed version, docs site, or demo video. Users want to see it running.

  2. 2
    README12pt

    Add CI/build status badges from shields.io or your CI provider to signal project health.

  3. 3
    Install and run instructions9pt

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

  4. 4
    Reproducibility6pt

    Add a Dockerfile, .nvmrc, or .python-version to pin the runtime version and make the environment reproducible.

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

80

Contributing guide5pt64

Contributing guide is detailed and thorough.

README12pt70

README is present.

Install and run instructions9pt90

README documents how to install the project.

License6pt100

Licensed under MIT.

Engineering

96

Reproducibility6pt70

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

Tests18pt100

Test files detected (apps/cli/e2e/add.test.ts).

CI/CD14pt100

CI is configured (.github/workflows/check-cli.yml).

Linting and formatting5pt100

Linter or formatter configured (biome.jsonc).

Issue and PR templates6pt100

Issue or PR templates present.

Project health

89

Dependency manifest6pt65

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)
  • 1
    Forks
  • 8
    Releaseslatest 1mo ago

Community

  • -
    Community health
  • -
    authors own >50% of commits
  • 13
    Watchers

Responsiveness

  • 2h
    Median issue response
  • <1h
    Median PR merge time
  • 10
    Open issues
Repository files26 root entries
  • .agents
  • .changeset
  • .devcontainer
  • .docs
  • .github
    Good: CI is configured (.github/workflows/check-cli.yml).
    Good: Issue or PR templates present.
  • .vscode
  • apps
    Good: Test files detected (apps/cli/e2e/add.test.ts).
  • media
  • packages
  • .envrc
  • .gitattributes
  • .gitignore
    Good: .gitignore present.
  • AGENTS.md
  • biome.jsonc
    Good: Linter or formatter configured (biome.jsonc).
  • bun.lock
    Good: Lockfile present (bun.lock). Installs are reproducible.
  • bunfig.toml
  • 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.
    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.
  • flake.lock
  • flake.nix
  • LICENSE
    Good: Licensed under MIT.
  • 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.
    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.
    Good: README documents how to install the project.
    Good: README documents how to run the project.
  • stack.effect.json
  • tsconfig.json
  • turbo.json
  • vitest.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/lloydrichards/stack-effect)](https://www.repo-grade.com/report/lloydrichards/stack-effect)

More graded TypeScript repos