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

[PR #52] [CLOSED] [Snyk] Fix for 1 vulnerable dependency path #72

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

📋 Pull Request Information

Original PR: https://github.com/sobolevn/awesome-cryptography/pull/52
Author: @snyk-bot
Created: 11/16/2017
Status: ❌ Closed

Base: master ← Head: snyk-fix-26390496

📝 Commits (1)

  • 9aee770 fix: package.json & .snyk to reduce vulnerabilities

📊 Changes

2 files changed (+16 additions, -3 deletions)

View changed files

➕ .snyk (+9 -0)
📝 package.json (+7 -3)

📄 Description

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

The PR includes:

  • package.json scripts and a Snyk policy (.snyk) file, which patch the vulnerabilities that can't be upgraded away and ignore vulnerabilities with no fixes.

Vulnerabilities that will be ignored for 30 days

No sufficient upgrades or patches are available. You’ll receive an alert when more fixes are released.

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

🔄 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/52 **Author:** [@snyk-bot](https://github.com/snyk-bot) **Created:** 11/16/2017 **Status:** ❌ Closed **Base:** `master` ← **Head:** `snyk-fix-26390496` --- ### 📝 Commits (1) - [`9aee770`](https://github.com/sobolevn/awesome-cryptography/commit/9aee770fd4bbe4f9b27539487b1f05f97009a6ce) fix: package.json & .snyk to reduce vulnerabilities ### 📊 Changes **2 files changed** (+16 additions, -3 deletions) <details> <summary>View changed files</summary> ➕ `.snyk` (+9 -0) 📝 `package.json` (+7 -3) </details> ### 📄 Description This pull request fixes one or more vulnerable packages in the npm dependencies of this project. See the [Snyk test report](https://snyk.io/test/github/sobolevn/awesome-cryptography) for this project for details. The PR includes: - `package.json` scripts and a Snyk policy (`.snyk`) file, which patch the vulnerabilities that can't be upgraded away and ignore vulnerabilities with no fixes. #### Vulnerabilities that will be ignored for 30 days No sufficient upgrades or patches are available. You’ll receive an alert when more fixes are released. - [npm:string:20170907](https://snyk.io/vuln/npm:string:20170907) 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 <!-- snyk:metadata:{"type":"fix","packageManager":"npm","vulns":["npm:string:20170907"],"patch":[],"ignore":["npm:string:20170907"],"upgrade":[],"isBreakingChange":false,"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:07:48 -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#72
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?