This repository has been archived by the owner on Nov 1, 2022. It is now read-only.
Configure Snyk protect to enable patches #21
Conversation
This file contains 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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
We noticed that you have patches available for this project, however it seems that
snyk protectis not properly configured.We're adding
snyk protectin order to patch your code and make it more secure.If you intentionally removed
snyk protect, then you can close this PR instead.If you are using a lockfile please pull down this branch and update the lockfile by running
npm ioryarn install.PS. We'd love to find out what you think about snyk protect, especially if it hasn't proved useful. Please get in touch via support@snyk.io