boostsecurityio/Scanner Registry Test Action
Run scanner tests when changes are made to the scanner registry
View on GitHubTrust Signals
- Scorecard Score
- not yet scored
- Maintenance Recency
- Activelast commit Feb 5, 2026
- License
- None
Pinned Snippet
uses: boostsecurityio/scan-test-action@05297ee358226347a9f4989716ffeb7ba1dedc4f # no releases — HEAD as of 2026-07-11tags can be moved; commit SHAs can't. why a SHA?
Inputs
| name | description | required | default |
|---|---|---|---|
| provider | CI/CD provider to use (github-actions, gitlab-ci, azure-devops, bitbucket) | yes | — |
| provider-config | JSON configuration for the selected provider. See README for schema per provider. | yes | — |
| registry-path | Path to scanner registry repository | yes | . |
| registry-repo | Registry repository identifier (org/repo format). For fork PRs, use the fork repo. | yes | — |
| registry-ref | Git ref of the registry (commit SHA). For fork PRs, use the fork SHA. | yes | — |
| base-ref | Base git reference to compare against. For fork PRs, use the base SHA. | yes | origin/main |
| fallback-scanners | Comma-separated scanner IDs to test when workflow files change but no scanner files changed | no | "" |
| allowed-env-prefixes | Comma-separated list of allowed environment variable prefixes for tests | no | "" |
Outputs
| name | description |
|---|---|
| results | JSON-formatted test results |