github-starred/awesome-cryptography
2
0
Fork 0
mirror of https://github.com/sobolevn/awesome-cryptography.git synced 2026-03-12 01:54:54 -05:00
Code Issues 29 Packages Projects Releases Wiki Activity

[PR #67] [MERGED] [Snyk] Fix for 1 vulnerable dependencies #86

New Issue
Closed
opened 2025-11-06 09:08:26 -06:00 by GiteaMirror · 0 comments
GiteaMirror commented 2025-11-06 09:08:26 -06:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/sobolevn/awesome-cryptography/pull/67
Author: @snyk-bot
Created: 10/22/2018
Status: ✅ Merged
Merged: 10/23/2018
Merged by: @sobolevn

Base: master ← Head: snyk-fix-kl4f4h

📝 Commits (1)

  • d125091 fix: package.json to reduce vulnerabilities

📊 Changes

1 file changed (+1 additions, -1 deletions)

View changed files

📝 package.json (+1 -1)

📄 Description

Description

This PR fixes one or more vulnerable packages in the npm dependencies of this project.
See the Snyk test report for more details.

Snyk Project: sobolevn/awesome-cryptography:package.json

Snyk Organization: wemake-services

Lockfile

If you are using package-lock.json or yarn.lock, please re-lock your dependencies and push an updated lockfile before merging this PR.

Changes included in this PR

  • Changes to the following files to upgrade the vulnerable dependencies to a fixed version:
    • package.json

Vulnerabilities that will be fixed

With an upgrade:

You can read more about Snyk's upgrade and patch logic in Snyk's documentation.

Check the changes in this PR to ensure they won't cause issues with your project.

Stay secure,
The Snyk team

Note: You are seeing this because you or someone else with access to this repository has authorised Snyk to open Fix PRs. To review the settings for this Snyk project please go to the project settings page.

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/sobolevn/awesome-cryptography/pull/67 **Author:** [@snyk-bot](https://github.com/snyk-bot) **Created:** 10/22/2018 **Status:** ✅ Merged **Merged:** 10/23/2018 **Merged by:** [@sobolevn](https://github.com/sobolevn) **Base:** `master` ← **Head:** `snyk-fix-kl4f4h` --- ### 📝 Commits (1) - [`d125091`](https://github.com/sobolevn/awesome-cryptography/commit/d12509171e367bc09bb155436b87c09cab9cf033) fix: package.json to reduce vulnerabilities ### 📊 Changes **1 file changed** (+1 additions, -1 deletions) <details> <summary>View changed files</summary> 📝 `package.json` (+1 -1) </details> ### 📄 Description #### Description This PR fixes one or more vulnerable packages in the `npm` dependencies of this project. See the [Snyk test report](https://app.snyk.io/org/wemake-services/test/github/ba636a2c-d0ef-42a3-b751-723ce94c5e38/master..snyk-fix-kl4f4h) for more details. #### Snyk Project: [sobolevn/awesome-cryptography:package.json](https://app.snyk.io/org/wemake-services/project/ba636a2c-d0ef-42a3-b751-723ce94c5e38) #### Snyk Organization: [wemake-services](https://app.snyk.io/org/wemake-services) #### Lockfile If you are using `package-lock.json` or `yarn.lock`, please re-lock your dependencies and push an updated lockfile before merging this PR. #### Changes included in this PR - Changes to the following files to upgrade the vulnerable dependencies to a fixed version: - package.json #### Vulnerabilities that will be fixed ##### With an upgrade: - [npm:braces:20180219](https://snyk.io/vuln/npm:braces:20180219) - potentially breaking change You can read more about Snyk's upgrade and patch logic in [Snyk's documentation](https://snyk.io/docs/using-snyk/). Check the changes in this PR to ensure they won't cause issues with your project. Stay secure, The Snyk team _**Note**: You are seeing this because you or someone else with access to this repository has authorised Snyk to open Fix PRs. To review the settings for this Snyk project please go to the [project settings page](https://app.snyk.io/org/wemake-services/project/ba636a2c-d0ef-42a3-b751-723ce94c5e38/settings)._ [//]: # (snyk:metadata:{"type":"auto","packageManager":"npm","vulns":["npm:braces:20180219"],"patch":[],"upgrade":["npm:braces:20180219"],"isBreakingChange":true,"env":"prod"}) --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
GiteaMirror added the pull-request label 2025-11-06 09:08:26 -06:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
content-request
enhancement
foreign-invalid-link
help wanted
pull-request
Mirrored from GitHub Pull Request
 question
section-request
waits-feedback
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/awesome-cryptography#86
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?