Solid foundation. Invest in docs and CI to grow from here.
Introduces a comprehensive agent-based framework for guided software development (GSD)
Documentation
85
README is present.
README documents how to install the project.
Contributing guide is detailed and thorough.
Licensed under Other.
Engineering
72
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 (package-lock.json). Installs are reproducible.
Test files detected (.college/calibration/delta-store.test.ts).
CI is configured (.github/workflows/ci.yml).
Linter or formatter configured (.editorconfig).
Project health
100
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)
- 8Forks
- 0Releases
Community
- —Community health
- —authors own >50% of commits
- 65Watchers
Responsiveness
- 18hMedian issue response
- <1hMedian PR merge time
- 0Open issues
Repository files53 root entries
- .collegeGood: Test files detected (.college/calibration/delta-store.test.ts).
- .githubGood: CI is configured (.github/workflows/ci.yml).
- apps
- benchmarks
- cartridges
- config
- contrib
- coprocessors
- dashboard
- data
- desktop
- dist
- docs
- examples
- extra
- infra
- migrations
- packaging
- packs
- project-claude
- projects
- proofs
- scripts
- skills
- src
- src-tauri
- tests
- tools
- .editorconfigGood: Linter or formatter configured (.editorconfig).
- .gitattributes
- .gitignoreGood: .gitignore present.
- .mcp.json
- .npmrc
- CHANGELOG.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.
- ERDOS-TRACKER.md
- INSTALL.md
- INVENTORY-MANIFEST.json
- LICENSEGood: Licensed under Other.
- Makefile
- package-lock.jsonGood: Lockfile present (package-lock.json). Installs are reproducible.
- package.jsonGood: Dependency manifest found (package.json).
- 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.
- release-history.config.json
- release-history.local.json.example
- SECURITY.mdGood: Security policy present.
- STANDING-RULES.md
- tsconfig.json
- typedoc.json
- vitest.bench.config.mjs
- vitest.config.ts
- vitest.dashboard.config.mjs
- vitest.tools.config.mjs