chore: add more tests, fuzzing, and a separate fuzz Workflow #1352
Merged
egibs merged 2 commits intochainguard-dev:mainfrom Feb 4, 2026
Merged
chore: add more tests, fuzzing, and a separate fuzz Workflow #1352egibs merged 2 commits intochainguard-dev:mainfrom
egibs merged 2 commits intochainguard-dev:mainfrom
Conversation
1c05005 to
b04ef1f
Compare
31d6a27 to
0a9a4ef
Compare
Signed-off-by: egibs <20933572+egibs@users.noreply.github.com>
0a9a4ef to
78ddb8a
Compare
eslerm
approved these changes
Feb 4, 2026
Contributor
eslerm
left a comment
There was a problem hiding this comment.
Looks good. Nice fuzzing workflow. Note some rule name changes. Fuzzing workflow may desire harden-runner. Instead of on push, may be best as cron. I had a friend setup fuzzing to use up any free ci left over.
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.
This PR adds additional testing and fuzzing coverage for some of the core functionality. Some of what malcontent does is harder to test outside of running a refresh or actual scans, but this will give us additional confidence that the basic concepts are behaving as they should.
It was also getting a little unwieldy to run so manny fuzzers serially during CI so I added a separate Workflow to run these on push to main, on a schedule, and via
workflow_dispatch.Of note, some of the tests resulted in small tweaks to general functionality which is exactly the point of having this kind of coverage. The main change here is how some third-party rules are rendered.