ansible/APME Check
Scan Ansible content against a hosted APME deployment — policy, modernization, secrets, collection health, and dependency audit
View on GitHubTrust Signals
- Scorecard Score
- not yet scored
- Maintenance Recency
- Activelast commit Jul 9, 2026
- License
- Apache 2.0
Pinned Snippet
uses: ansible/apme@c57eed18814194057b3c85465ff3cbbc1f6075a0 # v2026.7.3tags can be moved; commit SHAs can't. why a SHA?
Inputs
| name | description | required | default |
|---|---|---|---|
| target | Path to scan (file, directory, or project root) | no | . |
| ansible-version | ansible-core version to validate against (e.g. 2.18, 2.20) | no | "" |
| collections | Space-separated collection specs (e.g. community.general:9.0.0) | no | "" |
| args | Additional arguments passed to apme check | no | "" |
| primary-address | Primary gRPC address for the hosted APME deployment (host:port) | yes | — |
| sarif | Upload SARIF to GitHub Code Scanning (requires security-events:write) | no | true |
| upload-artifact | Upload JSON results as a workflow artifact | no | false |
| comment | Post a PR summary comment (requires pull-requests:write) | no | true |
| cli-version | Pin the apme-engine version (e.g. "0.1.0"). Defaults to latest release when empty. | no | "" |
Outputs
| name | description |
|---|---|
| exit-code | APME exit code: 0=clean, 1=violations, 2=error |
| violation-count | Number of violations found |
| sarif-path | Path to SARIF file (if generated) |