Repository navigation
Add Semgrep SAST workflow - #39
Merged
Merged
Conversation
Runs Semgrep (p/default) on every PR to main. PRs are diff-aware, so only findings a PR introduces fail the check. Pushes to main run a full, report-only scan. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01NgEiZxpTQEsuZCXUbkYwXe
quinnmil
marked this pull request as ready for review
November 2, 2026 23:09
mitchh456
approved these changes
Nov 2, 2026
mitchh456
left a comment
There was a problem hiding this comment.
Trigger is main, which matches the default branch and release.yml. The checkout SHA resolves to v6.1.0, and the image and pins match the apm copy.
This branch was successfully deployed
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
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.
Why
Adds a static analysis check to every PR on
main, so new security issues are caught before merge.What
.github/workflows/semgrep.ymlwith one job,Semgrep SAST: Semgrep'sp/defaultruleset in the pinnedsemgrep/semgrep:1.183.0image, metrics off, read-only token, 15 min timeout.--baseline-commit= the PR base), so only findings a PR introduces fail the check. The existing backlog doesn't block merges.mainrun a full, report-only scan. Also runnable viaworkflow_dispatch.Merging runs
On the push to
main:Publish distribution to PyPI: builds the package, thenpublish-to-testpypiuploads to Test PyPI withskip-existing. 1.0.4 is already there, so that's a no-op.publish-to-pypionly runs onv*tags, so nothing is released.Semgrep SASTfull scan (report-only).Test and Lintonly runs on PRs. No deploys or releases.Follow-ups
None in this repo.
🤖 Generated with Claude Code
https://claude.ai/code/session_01NgEiZxpTQEsuZCXUbkYwXe