Add scan_ai_sast support#99
Merged
Merged
Conversation
Adds a new `scan_ai_sast` input to the scan action, following the same pattern as `scan_sast` and `scan_secrets`. Passes `--ai-sast=true` to endorctl when enabled, includes it in the at-least-one validation guard, and blocks it from being combined with `scan_package`. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
- Pin lodash to >=4.18.0 (fixes high-severity Code Injection and Prototype Pollution CVEs) - Add brace-expansion >=5.0.5 resolution (fixes moderate DoS CVE in @actions/artifact chain) - Bump fast-xml-parser resolution to >=5.7.0 - Rebuild dist bundles Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
dpowley
approved these changes
May 28, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
scan_ai_sastboolean input toaction.yml(defaultfalse), following the same pattern asscan_sastandscan_secrets--ai-sast=truetoendorctlwhen enabledscan_ai_sastin the at-least-one scan type validation guardscan_ai_sastfrom being combined withscan_package(consistent with other scan types)dist/index.jsbundleTest plan
scan_ai_sast: truein a workflow and verify--ai-sast=trueis passed to endorctlscan_ai_sastandscan_packageproduces the expected conflict error🤖 Generated with Claude Code