Skip to content
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

[Snyk] Security upgrade svelte-check from 3.8.6 to 4.0.0 #36

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

naiba4
Copy link
Owner

@naiba4 naiba4 commented Sep 2, 2024

snyk-top-banner

Snyk has created this PR to fix 1 vulnerabilities in the npm dependencies of this project.

Snyk changed the following file(s):

  • packages/create-svelte/shared/+checkjs/package.json

Vulnerabilities that will be fixed with an upgrade:

Issue Score
medium severity Missing Release of Resource after Effective Lifetime
SNYK-JS-INFLIGHT-6095116
  141  

Important

  • Check the changes in this PR to ensure they won't cause issues with your project.
  • Max score is 1000. Note that the real score may have changed since the PR was raised.
  • This PR was automatically created by Snyk using the credentials of a real user.

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
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic


Learn how to fix vulnerabilities with free interactive lessons:

🦉 Learn about vulnerability in an interactive lesson of Snyk Learn.

Copy link

changeset-bot bot commented Sep 2, 2024

⚠️ No Changeset found

Latest commit: cf2d8ad

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

Copy link

New and removed dependencies detected. Learn more about Socket for GitHub ↗︎

Package New capabilities Transitives Size Publisher
npm/cookie@0.6.0 None 0 23.7 kB dougwilson

View full report↗︎

Copy link

🚨 Potential security issues detected. Learn more about Socket for GitHub ↗︎

To accept the risk, merge this PR and you will not be notified again.

Alert Package NoteSourceCI
New author npm/estraverse@4.3.0 🚫
Unmaintained npm/safer-buffer@2.1.2
  • Last Publish: 4/8/2018, 10:42:42 AM
🚫
Unmaintained npm/is-extglob@2.1.1
  • Last Publish: 12/11/2016, 4:04:24 AM
🚫
Debug access npm/pirates@4.0.6 🚫
New author npm/convert-source-map@2.0.0 🚫
Filesystem access npm/isexe@2.0.0 🚫
Environment variable access npm/isexe@2.0.0 🚫
Unmaintained npm/esprima@4.0.1
  • Last Publish: 7/13/2018, 8:39:14 AM
🚫
Unmaintained npm/reusify@1.0.4
  • Last Publish: 1/26/2018, 9:28:18 AM
🚫
Unmaintained npm/json-buffer@3.0.1
  • Last Publish: 9/10/2018, 7:02:16 PM
🚫
Debug access npm/builtin-modules@3.3.0 🚫
Unmaintained npm/get-caller-file@2.0.5
  • Last Publish: 3/9/2019, 9:48:30 PM
🚫
Filesystem access npm/y18n@5.0.8 🚫
Unmaintained npm/is-number@7.0.0
  • Last Publish: 7/4/2018, 3:08:58 PM
🚫
Unmaintained npm/any-promise@1.3.0
  • Last Publish: 5/8/2016, 12:15:06 PM
🚫
Trivial Package npm/min-indent@1.0.1 🚫
Unmaintained npm/natural-compare-lite@1.4.0
  • Last Publish: 10/26/2015, 11:53:58 AM
🚫

View full report↗︎

Next steps

What is new author?

A new npm collaborator published a version of the package for the first time. New collaborators are usually benign additions to a project, but do indicate a change to the security surface area of a package.

Scrutinize new collaborator additions to packages because they now have the ability to publish code into your dependency tree. Packages should avoid frequent or unnecessary additions or changes to publishing rights.

What are unmaintained packages?

Package has not been updated in more than 5 years and may be unmaintained. Problems with the package may go unaddressed.

Package should publish periodic maintenance releases if they are maintained, or deprecate if they have no intention in further maintenance.

What is debug access?

Uses debug, reflection and dynamic code execution features.

Removing the use of debug will reduce the risk of any reflection and dynamic code execution.

What is filesystem access?

Accesses the file system, and could potentially read sensitive data.

If a package must read the file system, clarify what it will read and ensure it reads only what it claims to. If appropriate, packages can leave file system access to consumers and operate on data passed to it instead.

What is environment variable access?

Package accesses environment variables, which may be a sign of credential stuffing or data theft.

Packages should be clear about which environment variables they access, and care should be taken to ensure they only access environment variables they claim to.

What are trivial packages?

Packages less than 10 lines of code are easily copied into your own project and may not warrant the additional supply chain risk of an external dependency.

Removing this package as a dependency and implementing its logic will reduce supply chain risk.

Take a deeper look at the dependency

Take 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 package

If 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 risk

To ignore an alert, reply with a comment starting with @SocketSecurity ignore followed by a space separated list of ecosystem/package-name@version specifiers. e.g. @SocketSecurity ignore npm/foo@1.0.0 or ignore all packages with @SocketSecurity ignore-all

  • @SocketSecurity ignore npm/estraverse@4.3.0
  • @SocketSecurity ignore npm/safer-buffer@2.1.2
  • @SocketSecurity ignore npm/is-extglob@2.1.1
  • @SocketSecurity ignore npm/pirates@4.0.6
  • @SocketSecurity ignore npm/convert-source-map@2.0.0
  • @SocketSecurity ignore npm/isexe@2.0.0
  • @SocketSecurity ignore npm/esprima@4.0.1
  • @SocketSecurity ignore npm/reusify@1.0.4
  • @SocketSecurity ignore npm/json-buffer@3.0.1
  • @SocketSecurity ignore npm/builtin-modules@3.3.0
  • @SocketSecurity ignore npm/get-caller-file@2.0.5
  • @SocketSecurity ignore npm/y18n@5.0.8
  • @SocketSecurity ignore npm/is-number@7.0.0
  • @SocketSecurity ignore npm/any-promise@1.3.0
  • @SocketSecurity ignore npm/min-indent@1.0.1
  • @SocketSecurity ignore npm/natural-compare-lite@1.4.0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants