lacework/lacework-code-security
Scan code with Lacework's Code Security offering
View on GitHubTrust Signals
- Scorecard Score
- not yet scored
- Maintenance Recency
- Activelast commit Jun 29, 2026
- License
- Apache 2.0
Pinned Snippet
uses: lacework/code-security-action@2c78d64a156f73487dd6d32754886e0df12899d3 # v1tags can be moved; commit SHAs can't. why a SHA?
Inputs
| name | description | required | default |
|---|---|---|---|
| sources | Sources directory to analyze | no | . |
| target | One of push, old or new to represent which is being analyzed | no | — |
| token | Set to a GitHub token for the repository with write permissions for PRs to enable PR comments | no | — |
| footer | A block of Markdown that will be appended to any PR comments posted | no | — |
| code-scanning-path | Path to write code scanning SARIF file | no | code-scanning.sarif |
Outputs
| name | description |
|---|---|
| old-completed | If running a target called old, whether the analysis for this was completed |
| new-completed | If running a target called new, whether the analysis for this was completed |
| push-completed | If running a target called push, whether the analysis for this was completed |
| display-completed | If displaying results, whether this was completed |
| comment-posted | If a comment was posted, a link to this comment |