mirror of
https://github.com/spamscanner/spamscanner.git
synced 2026-04-27 12:45:50 +03:00
[PR #24] [CLOSED] [Snyk] Security upgrade email-regex-safe from 1.0.2 to 2.0.0 #26
Labels
No labels
bug
bug
enhancement
help wanted
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/spamscanner#26
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
📋 Pull Request Information
Original PR: https://github.com/spamscanner/spamscanner/pull/24
Author: @titanism
Created: 2/11/2024
Status: ❌ Closed
Base:
master← Head:snyk-fix-e485913811a1a5163568193c35fd37b4📝 Commits (1)
7c84a83fix: package.json to reduce vulnerabilities📊 Changes
1 file changed (+1 additions, -1 deletions)
View changed files
📝
package.json(+1 -1)📄 Description
This PR was automatically created by Snyk using the credentials of a real user.
Snyk has created this PR to fix one or more vulnerable packages in the `yarn` dependencies of this project.
Changes included in this PR
Note for zero-installs users
If you are using the Yarn feature zero-installs that was introduced in Yarn V2, note that this PR does not update the
.yarn/cache/directory meaning this code cannot be pulled and immediately developed on as one would expect for a zero-install project - you will need to runyarnto update the contents of the./yarn/cachedirectory.If you are not using zero-install you can ignore this as your flow should likely be unchanged.
⚠️ Warning
Vulnerabilities that will be fixed
With an upgrade:
Why? Proof of Concept exploit, Recently disclosed, Has a fix available, CVSS 8.6
SNYK-JS-IP-6240864
(*) Note that the real score may have changed since the PR was raised.
Check the changes in this PR to ensure they won't cause issues with your project.
Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.
For more information:
🧐 View latest project report
🛠 Adjust project settings
📚 Read more about Snyk's upgrade and patch logic
Learn how to fix vulnerabilities with free interactive lessons:
🦉 Server-side Request Forgery (SSRF)
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.