zivrio/Boop Code Quality
Scan your code and run quality gate checks with Boop — cloud-powered code intelligence.
View on GitHubTrust Signals
- Scorecard Score
- not yet scored
- Maintenance Recency
- Stale
- License
- None
Inputs
| name | description | required | default |
|---|---|---|---|
| project-key | Project-scoped API key (recommended for CI). Grants access only to this project's scan and check operations. Generate one with `boop project keys`. Takes precedence over api-key. | no | — |
| api-key | Full account API key. Use project-key instead when possible — it limits blast radius if the secret is ever exposed. | no | — |
| project-id | Boop project ID (UUID). Only required if .boop/config.json is not committed to the repository. | no | — |
| category | Check category to run. One of: security, complexity, quality, all. | no | all |
| scan | Whether to re-index changed files before running checks. Set to 'false' to run checks against the existing index only (faster, but results may be stale if code changed). | no | true |
| fail-on | Severity level that causes a non-zero exit code. errors — fail only on error-severity checks (default). warnings — fail on warnings and errors (strict mode). never — always exit 0, even if checks fail (advisory only). | no | errors |
| version | Boop CLI version to install. Defaults to 'latest'. Pin to a specific version (e.g. '0.1.2') for reproducible builds. | no | latest |
Outputs
| name | description |
|---|---|
| issues | Total number of issues found across all checks. |
| result | Overall result — 'passed' or 'failed'. |