fix: skip npm audit signatures for packages from private registry#39
Merged
Merged
Conversation
…PR not supported)
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
1 participant
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.
npm audit signaturesonly supports packages installed from npmjs.com. The deploy-config-schema package is installed from GHPR (npm.pkg.github.com), which causes npm to exit with "found no dependencies to audit that were installed from a supported registry". This is expected behavior, not a signature failure.The fix treats that specific error message as a non-blocking warning (provenance_verified=false) rather than a hard failure. Any other npm audit error still fails hard.