Strong early engineering with some momentum.
Self-triggering, skill-based agentic methodology: agents, skills, commands, hooks and protocols
Documentation
92
Contributing guide is detailed and thorough.
README is present.
README documents how to install the project.
Licensed under Apache-2.0.
Engineering
69
No linter or formatter config found.
→ Add a linter config such as .eslintrc.json, .prettierrc, ruff.toml, or .golangci.yml to enforce consistent code style.
CI is configured (.github/workflows/adapter-sync.yml).
Test files detected (bin/tests).
Lockfile present (scripts/package-lock.json). Installs are reproducible.
Issue or PR templates present.
Project health
100
Dependency manifest found (scripts/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
- 0Releases
Community
- —Community health
- —authors own >50% of commits
- 10Watchers
Responsiveness
- —Median issue response
- <1hMedian PR merge time
- 20Open issues
Repository files40 root entries
- .claude
- .codex
- .cursor
- .gemini
- .githubGood: CI is configured (.github/workflows/adapter-sync.yml).Good: Dependabot covers 2 ecosystems (npm, github-actions). Dependencies stay current.Good: Issue or PR templates present.
- .hermes
- .kimi
- .omp
- .openclaw
- .opencode
- .pi
- binGood: Test files detected (bin/tests).
- content
- docs
- hooks
- scriptsGood: Lockfile present (scripts/package-lock.json). Installs are reproducible.Good: Dependency manifest found (scripts/package.json).
- .gitignoreGood: .gitignore present.
- .gitleaks.toml
- .mailmap
- ADAPTERS.md
- AGENTS.md
- bootstrap.sh
- CHANGELOG.md
- CLAUDE.md
- CODE_OF_CONDUCT.mdGood: Code of conduct present.
- 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.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).Good: Contributing guide describes the PR/review workflow.Good: Contributing guide includes code examples.
- GOVERNANCE.md
- install-all.sh
- LICENSEGood: Licensed under Apache-2.0.
- MAINTAINERS.md
- MEMORY.md
- NOTICE
- 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.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.
- ROADMAP.md
- SAFETY.md
- SECURITY.mdGood: Security policy present.
- SUPPORT.md
- THIRD_PARTY_NOTICES.md
- update.sh
- vercel.json