97/ 100 · A
Impressive early momentum. Already polished and picking up traction fast.
A powerful meta-prompting, context engineering and spec-driven development system that enables agents to work for long periods of time autonomously without losing track of the big picture
TypeScript729 starsMITupdated today
Outstanding work. A score of 97/100 puts this repo in a very small tier of truly well-engineered open source projects.
DocumentationREADME, setup, examples, license
EngineeringTests, CI, linting, lockfiles
Project healthDescription, activity, stars, deps
What to fix first
The highest-impact improvements for this repo.
- 1CI/CDEngineeringIssue
Add a lint step to catch style issues automatically.
- 2CI/CDEngineeringInfo
Add `tsc --noEmit`, `mypy`, or `cargo check` to catch type errors before they merge.
- 3CI/CDEngineeringInfo
Upload coverage to Codecov, Coveralls, or report it with `--coverage` flags.
Detailed breakdown
Documentation
99- README100
- README is present.
- README is well structured with multiple sections.
- README includes screenshots or visuals. Great for first impressions.
- README has code examples.
- README links to a live demo or deployed app.
- README includes status badges.
- Install and run instructions100
- README documents how to install the project.
- README documents how to run the project.
- .env.example is present. Contributors can see exactly which env vars to set.
- License100
- Licensed under MIT.
- Contributing guide92
- Contributing guide is detailed and thorough.
- Contributing guide includes setup/install instructions.
- Contributing guide lacks a code style section (−8 pts).Describe your linting/formatting rules and how to run them.
- Contributing guide explains how to run tests.
- Contributing guide describes the PR/review workflow.
- Contributing guide includes code examples.
- Optional: add a Code of Conduct.A CODE_OF_CONDUCT.md signals that your project is welcoming. GitHub has a template you can add in one click.
Engineering
96- Tests100
- Test files detected (packages/cloud-mcp-gateway/src/auth-store.test.ts).
- CI/CD85
Not applicable?
- CI is configured (.github/workflows/build-native.yml).
- CI workflow runs tests.
- CI runs on pull requests, not just on pushes to main.
- CI does not run a lint or format check (−15 pts).Add a lint step to catch style issues automatically.
- Optional: add type checking to CI.Add `tsc --noEmit`, `mypy`, or `cargo check` to catch type errors before they merge.
- Optional: report test coverage in CI.Upload coverage to Codecov, Coveralls, or report it with `--coverage` flags.
- CI caches dependencies for faster runs.
- CI tests across multiple environments or versions.
- CI includes a build step.
- Linting and formatting100
- Linter or formatter configured (web/eslint.config.mjs).
- Reproducibility100
- Lockfile present (pnpm-lock.yaml). Installs are reproducible.
- Environment pinned via Dockerfile.
- Dockerfile uses multi-stage builds (smaller, more secure images).
- Dependabot covers 3 ecosystems (npm, cargo, github-actions). Dependencies stay current.
- Issue and PR templates100
- Issue or PR templates present.
- Security policy present.
Project health
97- Dependency manifest92
- Dependency manifest found (package.json).
- package.json has a description field.
- package.json links back to the repository.
- package.json has no keywords (−8 pts).Add a `keywords` array to help people find your package on npm.
- Repository metadata100
- Repository has a description.
- Primary language detected: TypeScript.
- Activity100
- Actively maintained (pushed within the last month).
- 729 stars.
- Housekeeping100
- .gitignore present.
Repository health signals
Activity, community, and responsiveness at scan time
Activity
- —Commits (30d / 90d)
- 65Forks
- 5Releaseslatest 2d ago
Community
- —Community health
- —authors own >50% of commits
- 729Watchers
Responsiveness
- <1hMedian issue response
- <1hMedian PR merge time
- 17Open issues
Repository files39 root entries
- .githubGood: CI is configured (.github/workflows/build-native.yml).Good: Dependabot covers 3 ecosystems (npm, cargo, github-actions). Dependencies stay current.Good: Issue or PR templates present.
- .plans
- docker
- docs
- extensions
- gitbook
- gsd-orchestrator
- mintlify-docs
- native
- packagesGood: Test files detected (packages/cloud-mcp-gateway/src/auth-store.test.ts).
- pkg
- plans
- scripts
- srcGood: Security policy present.
- studio
- tests
- vscode-extension
- webGood: Linter or formatter configured (web/eslint.config.mjs).
- .dockerignore
- .gitignoreGood: .gitignore present.
- .npmignore
- .npmrc
- .prompt-injection-scanignore
- .secretscanignore
- CHANGELOG.md
- CONTEXT.md
- CONTRIBUTING.mdGood: 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.
- DockerfileGood: Environment pinned via Dockerfile.
- LICENSEGood: Licensed under MIT.
- package.jsonGood: Dependency manifest found (package.json).
- pnpm-lock.yamlGood: Lockfile present (pnpm-lock.yaml). Installs are reproducible.
- pnpm-workspace.yaml
- 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.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.
- screenshot-context-breakdown.jpg
- tsconfig.extensions.json
- tsconfig.json
- tsconfig.resources.json
- tsconfig.test.json
- VISION.md