AIPass is stable and built by a solo developer working with an AI team. Contributions are welcome.
Open an issue first. Use the issue templates for bug reports or general feedback. This lets us discuss scope and approach before you write code.
PRs are welcome after an issue has been discussed. Keep changes focused -- one fix or feature per PR. Include tests where applicable.
Target the dev branch. main only receives tested release trains from dev -- all work integrates on dev first (full test suite + standards audit), then rides a dev-to-main merge. GitHub defaults new PRs to main; switch the base to dev when you open one. If you forget, we'll retarget it -- your PR stays open either way.
Changes under src/aipass/spawn/templates/ also need the template registry regenerated (drone @spawn regenerate-registry) -- the registry tracks a content hash per template file and will report drift otherwise.
- Python 3.10+
- Tests:
pytest(4,900+ tests across the project) - Quality: AIPass uses its own standards system (sentry) for automated audits
- Run
./aipass install --no-finishto bootstrap the full environment without the health check and install report (contributors work in the engine repo itself) - To work on AIPass itself, run
claudeinsrc/aipass/devpulse, the orchestrator that plans and dispatches the work; it holds the repo's git write
Open a feedback issue or start a discussion in an existing thread.