0
/ 100
A well-known project done right. Strong docs and solid engineering throughout.
A Truman Show of a self-evolving AI coding agent. It writes its own code. Growing up in public.
Documentation
93
CONTRIBUTING guide found.
README documents how to install the project.
README is present.
Licensed under MIT.
Engineering
88
No Cargo.lock found (−70 pts). Rust binary/application crates should commit Cargo.lock.
→ Run `cargo build` and commit the resulting Cargo.lock file.
Test files detected (scripts/test_scan_commitments.py).
CI is configured (.github/workflows/ci.yml).
Rust linting configured (cargo clippy in CI, cargo fmt in CI).
Issue or PR templates present.
Project health
100
Dependency manifest found (Cargo.toml).
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)
- 121Forks
- 8Releaseslatest 1mo ago
Community
- -Community health
- -authors own >50% of commits
- 1,829Watchers
Responsiveness
- 11hMedian issue response
- -Median PR merge time
- 8Open issues
Repository files34 root entries
- .githubGood: CI is configured (.github/workflows/ci.yml).Good: Issue or PR templates present.
- .yoyo
- assets
- docsGood: CONTRIBUTING guide found.Issue: CONTRIBUTING guide contents could not be read (−28 pts vs a readable file).Fix: Move the file to the repo root or docs/CONTRIBUTING.md so its setup, style, test, and PR sections can be graded.
- dreams
- journals
- memory
- scriptsGood: Test files detected (scripts/test_scan_commitments.py).
- skills
- skills_attic
- sponsors
- src
- tests
- .dream_last_run
- .gitignoreGood: .gitignore present.
- .skill_evolve_counter
- .yoyo.toml
- build.rs
- Cargo.tomlGood: Dependency manifest found (Cargo.toml).
- CHANGELOG.md
- CLAUDE_CODE_GAP.md
- CLAUDE.md
- DAY_COUNT
- DREAM.md
- ECONOMICS.md
- IDENTITY.md
- install.ps1
- install.sh
- LICENSEGood: Licensed under MIT.
- LINEAGE.md
- mutants.toml
- PERSONALITY.md
- 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.
- SPONSORS.md