rebelopsio/Boundary Architecture Check
Run boundary architecture analysis and emit PR annotations for violations
View on GitHubTrust Signals
- Scorecard Score
- not yet scored
- Maintenance Recency
- Activelast commit Apr 16, 2026
- License
- MIT
Pinned Snippet
uses: rebelopsio/boundary-action@bc70b763070b6e2bfe8071fa31c1008001b7c5f4 # boundary-action-v0.1.2tags can be moved; commit SHAs can't. why a SHA?
Inputs
| name | description | required | default |
|---|---|---|---|
| path | Path to the project root to analyze | no | . |
| fail-on | Minimum severity to fail the check (error or warning) | no | error |
| config | Path to .boundary.toml config file | no | "" |
| languages | Comma-separated languages to analyze (empty = auto-detect) | no | "" |
| track | Save analysis snapshot for evolution tracking | no | false |
| no-regression | Fail if architecture score regresses from last snapshot | no | false |
| incremental | Use incremental analysis (cache unchanged files) | no | false |
| per-service | Analyze each service independently (monorepo mode) | no | false |
| boundary-version | Exact boundary release tag to install | no | 0.27.0 |
Outputs
| name | description |
|---|---|
| score | Overall architecture score (0-100) |
| violations | Total violation count |
| errors | Error-severity violation count |
| warnings | Warning-severity violation count |
| passed | "true" or "false" |