Popular for its size, but the engineering basics lag behind the interest.
Website of openclaw.ai
Documentation
60
No license detected.
→ Add a LICENSE file. Without one, nobody can legally use, copy, or contribute to your code.
Contributing guide is too short for full depth credit (−6 pts). 400+ words earns the full +12 pts.
→ Add setup instructions, code style notes, and how to run tests.
README is present.
README documents how to install the project.
Engineering
65
No linter or formatter found.
→ Add ESLint (eslint.config.js) and/or Prettier (.prettierrc), install them as devDependencies, and add a `lint` script to package.json.
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.
CI is configured (.github/workflows/install-git-smoke.yml).
Test files detected (tests).
Lockfile present (bun.lock). Installs are reproducible.
Project health
89
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)
- 203Forks
- 0Releases
Community
- —Community health
- —authors own >50% of commits
- 292Watchers
Responsiveness
- 5d 8hMedian issue response
- 1d 4hMedian PR merge time
- 0Open issues
Repository files17 root entries
- .githubGood: CI is configured (.github/workflows/install-git-smoke.yml).Good: Dependabot covers 6 ecosystems (github-actions, npm, docker, docker, docker, docker). Dependencies stay current.
- public
- scriptsGood: Environment pinned via scripts/docker/install-cli-git-smoke/Dockerfile.
- src
- testsGood: Test files detected (tests).
- .gitignoreGood: .gitignore present.
- .npmrc
- AGENTS.md
- astro.config.mjs
- bun.lockGood: Lockfile present (bun.lock). Installs are reproducible.
- CHANGELOG.md
- CLAUDE.md
- CONTRIBUTING.mdIssue: Contributing guide is too short for full depth credit (−6 pts). 400+ words earns the full +12 pts.Fix: Add setup instructions, code style notes, and how to run tests.Issue: Contributing guide lacks a setup section (−12 pts).Fix: Show new contributors how to get a local dev environment running.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).Issue: Contributing guide lacks a PR workflow section (−8 pts).Fix: Explain how to fork, branch, and open a pull request so contributors know what to expect.Issue: Contributing guide has no code examples (−5 pts).Fix: Add code blocks showing example commands for setup, running tests, and submitting a PR.
- 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.
- tsconfig.json
- vercel.json