Open
Conversation
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #1180 +/- ##
==========================================
+ Coverage 92.91% 93.14% +0.23%
==========================================
Files 171 172 +1
Lines 8329 8525 +196
==========================================
+ Hits 7739 7941 +202
+ Misses 590 584 -6
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
7e278ad to
f7b9705
Compare
sevbch
previously requested changes
Feb 24, 2026
f7b9705 to
75bde61
Compare
c34beee to
d94d897
Compare
6d7a
reviewed
Apr 15, 2026
Contributor
6d7a
left a comment
There was a problem hiding this comment.
I guess Mattis was faster than me 😁
Just one additional suggestion.
f8ee146 to
2ab66c9
Compare
6d7a
reviewed
Apr 16, 2026
2ab66c9 to
71fcce5
Compare
6d7a
approved these changes
Apr 16, 2026
Contributor
6d7a
left a comment
There was a problem hiding this comment.
LGTM. Thank you for the changes!
…re_mode Add keyless signature verification for plugin wheels using sigstore bundles with OIDC identity-based trust. Replace --force flag with --allow-unsigned and enterprise config signature mode support. Forward signature_mode through all download paths (GitHub release, GitHub artifact, URL, local wheel). Collapse repetitive install error tests into parametrized ones.
71fcce5 to
69d06b7
Compare
Everything has been taken into account :)
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.
Context
The plugin system shipped in 1.48.0 used a --force flag to skip security warnings when installing from non-GitGuardian sources. This was a placeholder — it displayed a text warning but performed no actual
cryptographic verification.
This PR replaces that mechanism with real sigstore-based signature verification for plugin wheels, using OIDC identity-based trust (keyless). It also fixes a bug where the verification mode was not forwarded
through the GitHub release and artifact download paths.
What has been done
STRICT (block unsigned/invalid), WARN (log and continue), DISABLED (skip).
enterprise config.
writing the manifest (was missing entirely).
parameterized test.
Validation
pdm run pytest tests/unit/core/plugin/ tests/unit/cmd/plugin/ -x -q
All 246 tests pass. To manually test signature verification:
PR check list
label has been added to the PR.