[Snyk] Upgrade promise-polyfill from 8.2.1 to 8.2.3 #324
Conversation
This file contains hidden or 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
Snyk has created this PR to upgrade promise-polyfill from 8.2.1 to 8.2.3. See this package in npm: https://www.npmjs.com/package/promise-polyfill See this project in Snyk: https://app.snyk.io/org/ahnan/project/4ce69d57-438a-4086-b40c-8fde1ac702ae?utm_source=github&utm_medium=referral&page=upgrade-pr
|
| GitGuardian id | Secret | Commit | Filename | |
|---|---|---|---|---|
| 1567095 | Generic High Entropy Secret | b6e7a4f | examples/js/tokengenerator.js | View secret |
| 1567095 | Generic High Entropy Secret | b6e7a4f | examples/js/tokengenerator.js | View secret |
| 3201838 | Generic High Entropy Secret | b6e7a4f | examples/js/tokengenerator.js | View secret |
🛠 Guidelines to remediate hardcoded secrets
- Understand the implications of revoking this secret by investigating where it is used in your code.
- Replace and store your secrets safely. Learn here the best practices.
- Revoke and rotate these secrets.
- If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.
To avoid such incidents in the future consider
- following these best practices for managing and storing secrets including API keys and other credentials
- install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.
🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.
Our GitHub checks need improvements? Share your feedbacks!
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR was automatically created by Snyk using the credentials of a real user.
Snyk has created this PR to upgrade promise-polyfill from 8.2.1 to 8.2.3.
ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.
Release notes
Package name: promise-polyfill
-
8.2.3 - 2022-03-12
-
8.2.2 - 2022-03-12
-
8.2.1 - 2021-10-22
from promise-polyfill GitHub release notesThis is the same code as 8.2.0. A bugfix was introduced in 8.2.1 to fix testing issues, but it caused IE11 to fail
Commit messages
Package name: promise-polyfill
Compare
Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.
For more information:
🧐 View latest project report
🛠 Adjust upgrade PR settings
🔕 Ignore this dependency or unsubscribe from future upgrade PRs