0
/ 100
Good shape overall. A few tweaks would push it into the top tier.
Mac-first workspace orchestrator for bootstrapping developer environments, managing shell startup, and coordinating commands across peer project repos.
Top fixes
Highest-impact changes first, ranked by point weight
- 1Tests18pt
Wire your tests to a documented command (e.g. a test script in your build config) so the suite is reproducible.
- 2Install and run instructions9pt
Add a .env.example listing all required environment variables so contributors know what to set up.
- 3Reproducibility6pt
Commit poetry.lock, uv.lock, pdm.lock, Pipfile.lock, conda-lock.yml, or another lockfile for your Python dependency manager.
- 4Reproducibility6pt
Add a Dockerfile, .nvmrc, or .python-version to pin the runtime version and make the environment reproducible.
Working through the fixes? Let every push regrade itself.
The free GitHub App rescans this repo on every push and posts the grade as a commit check, so the score climbs without coming back to rescan by hand.
Scorecard
Every check, grouped by category and sorted worst-first
Documentation
94
Contributing guide is detailed and thorough.
README documents how to install the project.
README is present.
Licensed under Other.
Engineering
80
No dependency lockfile found (−70 pts).
→ Commit poetry.lock, uv.lock, pdm.lock, Pipfile.lock, conda-lock.yml, or another lockfile for your Python dependency manager.
Test files detected (cli/bash/commands/basectl/tests).
CI is configured (.github/workflows/tests.yml).
Linter or formatter configured (.pylintrc).
Issue or PR templates present.
Project health
68
No dependency manifest detected at root.
→ Add a manifest (package.json, pyproject.toml, Cargo.toml, go.mod, etc.) so others can install dependencies in one command.
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)
- 13Forks
- 16Releaseslatest 1mo ago
Community
- -Community health
- -authors own >50% of commits
- 116Watchers
Responsiveness
- -Median issue response
- <1hMedian PR merge time
- 8Open issues
Repository files27 root entries
- .ai-context
- .githubGood: CI is configured (.github/workflows/tests.yml).Good: Issue or PR templates present.
- bin
- cliGood: Test files detected (cli/bash/commands/basectl/tests).
- demo
- docs
- lib
- templates
- tests
- .codexignore
- .gitignoreGood: .gitignore present.
- .pylintrcGood: Linter or formatter configured (.pylintrc).
- AGENTS.md
- base_init.sh
- base_manifest.yaml
- bootstrap.sh
- CHANGELOG.md
- CONTRIBUTING.mdGood: Contributing guide is detailed and thorough.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.Good: Contributing guide explains how to run tests.Good: Contributing guide describes the PR/review workflow.Good: Contributing guide includes code examples.
- FAQ.md
- install.sh
- LICENSEGood: Licensed under Other.
- pytest.ini
- 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.
- requirements-dev.txt
- skills.md
- STANDARDS.md
- VERSION
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/basefoundry/base)