0
/ 100
Strong setup for a brand-new repo. Docs and CI already in good shape.
GTM Grid — local-first programmable GTM spreadsheet. Columns are functions. Source-available (FSL-1.1).
Documentation
73
No CONTRIBUTING.md found (−47 pts base + up to −53 pts more for content).
→ Add a CONTRIBUTING.md telling newcomers how to get involved. Include setup, code style, test, and PR instructions.
README is present.
README documents how to install the project.
Licensed under Other.
Engineering
84
No issue or PR templates found (−100 pts).
→ Add .github/ISSUE_TEMPLATE/ with bug_report.md and feature_request.md to guide contributors. It dramatically improves issue quality.
Lockfile present (pnpm-lock.yaml). Installs are reproducible.
Test files detected (apps/web/app/api/worker/_schemas.test.ts).
CI is configured (.github/workflows/ci.yml).
Linter or formatter configured (apps/web/eslint.config.mjs).
Project health
92
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)
- 3Forks
- 98Releaseslatest 20d ago
Community
- -Community health
- -authors own >50% of commits
- 6Watchers
Responsiveness
- -Median issue response
- <1hMedian PR merge time
- 17Open issues
Repository files25 root entries
- .changeset
- .githubGood: CI is configured (.github/workflows/ci.yml).
- .turbo
- appsGood: Test files detected (apps/web/app/api/worker/_schemas.test.ts).Good: Linter or formatter configured (apps/web/eslint.config.mjs).
- bin
- docs
- extensions
- packages
- patches
- scripts
- supabase
- .env.example
- .gitignoreGood: .gitignore present.
- .oxlintrc.json
- DESIGN.md
- LICENSEGood: Licensed under Other.
- package.jsonGood: Dependency manifest found (package.json).
- pnpm-lock.yamlGood: Lockfile present (pnpm-lock.yaml). Installs are reproducible.
- pnpm-workspace.yaml
- posthog-setup-report.md
- README.mdGood: README is present.Good: README is well structured with multiple sections.Issue: No screenshots or images in the README (−20 pts).Fix: Add a GIF, screenshot, or logo image. It is the fastest way to show what your project does.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.
- tsconfig.base.json
- tsconfig.json
- turbo.json
- vitest.config.ts