Solid foundation. Invest in docs and CI to grow from here.
bb is an agentic IDE that can control itself
Documentation
85
Contributing guidance is in the README, not a dedicated CONTRIBUTING.md (−20 pts).
→ Moving it to a CONTRIBUTING.md makes it easier to find and keeps the README focused. A dedicated file earns +47 pts base.
README documents how to install the project.
README is present.
Licensed under MIT.
Engineering
73
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/build-desktop.yml).
Lockfile present (pnpm-lock.yaml). Installs are reproducible.
Test files detected (apps/app/src/components/git-diff/git-diff-parsing.test.ts).
Linter or formatter configured (eslint.config.mjs).
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)
- 5Forks
- 16Releaseslatest 20d ago
Community
- —Community health
- —authors own >50% of commits
- 59Watchers
Responsiveness
- —Median issue response
- <1hMedian PR merge time
- 11Open issues
Repository files26 root entries
- .githubGood: CI is configured (.github/workflows/build-desktop.yml).
- .hermes
- appsGood: Test files detected (apps/app/src/components/git-diff/git-diff-parsing.test.ts).
- assets
- docs
- packages
- plans
- qa
- scripts
- tests
- .bb-env-setup.sh
- .gitattributes
- .gitignoreGood: .gitignore present.
- .nvmrcGood: Environment pinned via .nvmrc.
- .prettierignore
- AGENTS.md
- CLAUDE.md
- eslint.config.mjsGood: Linter or formatter configured (eslint.config.mjs).
- 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.
- turbo.json
- vitest.config.ts
- vitest.shared.ts