-
-
Notifications
You must be signed in to change notification settings - Fork 0
[Snyk] Upgrade vscode-oniguruma from 1.3.1 to 2.0.1 #26
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Snyk has created this PR to upgrade vscode-oniguruma from 1.3.1 to 2.0.1. See this package in npm: vscode-oniguruma See this project in Snyk: https://app.snyk.io/org/dargon789/project/81223846-82c7-4392-ad06-d64b8cece886?utm_source=github&utm_medium=referral&page=upgrade-pr
Review or Edit in CodeSandboxOpen the branch in Web Editor • VS Code • Insiders |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Copilot wasn't able to review any files in this pull request.
Files not reviewed (2)
- standalone-packages/vscode-textmate/package-lock.json: Language not supported
- standalone-packages/vscode-textmate/package.json: Language not supported
Reviewer's Guide by SourceryThis pull request upgrades the Updated class diagram for vscode-textmate packageclassDiagram
class vscode-textmate {
dependencies: object
}
note for vscode-textmate "vscode-oniguruma dependency updated from 1.3.1 to 2.0.1"
File-Level Changes
Tips and commandsInteracting with Sourcery
Customizing Your ExperienceAccess your dashboard to:
Getting Help
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We have skipped reviewing this pull request. It seems to have been created by a bot ('[Snyk]' found in title). We assume it knows what it's doing!
🎉 Snyk checks have passed. No issues have been found so far.✅ security/snyk check is complete. No issues have been found. (View Details) |
🚨 Potential security issues detected. Learn more about Socket for GitHub ↗︎ To accept the risk, merge this PR and you will not be notified again.
Next stepsWhat is a deprecated package?The maintainer of the package marked it as deprecated. This could indicate that a single version should not be used, or that the package is no longer maintained and any new vulnerabilities will not be fixed. Research the state of the package and determine if there are non-deprecated versions that can be used, or if it should be replaced with a new, supported solution. What is a license policy violation?This package is not allowed per your license policy. Review the package's license to ensure compliance. Find a package that does not violate your license policy or adjust your policy to allow this package's license. What is a CVE?Contains a high severity Common Vulnerability and Exposure (CVE). Remove or replace dependencies that include known high severity CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies. What is a critical CVE?Contains a Critical Common Vulnerability and Exposure (CVE). Remove or replace dependencies that include known critical CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies. Take a deeper look at the dependencyTake a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support [AT] socket [DOT] dev. Remove the packageIf you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency. Mark a package as acceptable riskTo ignore an alert, reply with a comment starting with
|
Snyk has created this PR to upgrade vscode-oniguruma from 1.3.1 to 2.0.1.
ℹ️ 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.
The recommended version is 9 versions ahead of your current version.
The recommended version was released 2 years ago.
Release notes
Package name: vscode-oniguruma
Fix .d.ts (#21)
Build the wasm in the pipeline
Fix path
check out submodules in CI
Try to add emsdk paths to PATH
Try to simplify steps
update to newer emsdk version
Add emsdk dirs to PATH
Fix path
checkout submodule
Go back to main template
Ignore the entire build folder
v1.7.0 (#15)
1.6.2
1.6.1
1.6.0
1.5.1
1.5.0
1.4.0
1.3.1
Important
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:
Summary by Sourcery
Upgrade the vscode-oniguruma dependency from version 1.3.1 to 2.0.1
New Features:
Enhancements: