0
/ 100
Well engineered for its size. A portfolio piece worth showing off.
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.
Documentation
80
Contributing guide is detailed and thorough.
README is present.
README documents how to install the project.
Licensed under MIT.
Engineering
96
Lockfile present (bun.lock). Installs are reproducible.
Test files detected (apps/cli/e2e/add.test.ts).
CI is configured (.github/workflows/check-cli.yml).
Linter or formatter configured (biome.jsonc).
Issue or PR templates present.
Project health
89
Dependency manifest found (package.json).
Repository has a description.
Actively maintained (pushed within the last month).
.gitignore present.
Repository health signals
Activity, community, and responsiveness at scan time
Activity
- -Commits (30d / 90d)
- 1Forks
- 8Releaseslatest today
Community
- -Community health
- -authors own >50% of commits
- 13Watchers
Responsiveness
- 2hMedian issue response
- <1hMedian PR merge time
- 10Open issues
Repository files26 root entries
- .agents
- .changeset
- .devcontainer
- .docs
- .githubGood: CI is configured (.github/workflows/check-cli.yml).Good: Issue or PR templates present.
- .vscode
- appsGood: Test files detected (apps/cli/e2e/add.test.ts).
- media
- packages
- .envrc
- .gitattributes
- .gitignoreGood: .gitignore present.
- AGENTS.md
- biome.jsoncGood: Linter or formatter configured (biome.jsonc).
- bun.lockGood: Lockfile present (bun.lock). Installs are reproducible.
- bunfig.toml
- CONTRIBUTING.mdGood: 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
- LICENSEGood: Licensed under MIT.
- package.jsonGood: Dependency manifest found (package.json).
- README.mdGood: 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