This repository has been archived by the owner on Jun 10, 2022. It is now read-only.
Fix jwt vulnerabilities #1
Merged
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
|
The vulnerability is on the consumer side, not producer. This repo generates tokens, hence there is no vulnerability. |
|
I understand what you mean. Though the library does take care of both and is reporting warnings to NPM.
Since it sounds silly to split jsonwebtoken in 2 (consumer/producer) & there is no way make NPM distinguish between the usages of the library it would be great to update the dependency so we don't have to interpret the warnings given. |
Closed
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.
No description provided.