search

sanity-io / plugin-kit

Enhanced Sanity.io plugin development experience.
MIT License
76 stars 7 forks source link

fix(deps): Update dependency @sanity/pkg-utils to v6.6.1 #169

Closed renovate[bot] closed 7 months ago

renovate[bot] commented 7 months ago

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@sanity/pkg-utils 6.6.0 -> 6.6.1 age adoption passing confidence

Release Notes

sanity-io/pkg-utils (@​sanity/pkg-utils) ### [`v6.6.1`](https://togithub.com/sanity-io/pkg-utils/blob/HEAD/CHANGELOG.md#661-2024-04-11) [Compare Source](https://togithub.com/sanity-io/pkg-utils/compare/v6.6.0...v6.6.1) ##### Bug Fixes - add `parseStrictOptions` export ([#​734](https://togithub.com/sanity-io/pkg-utils/issues/734)) ([6b9e7a0](https://togithub.com/sanity-io/pkg-utils/commit/6b9e7a0a561c49bb09816ce34a3f9247b51f78a0))

Configuration

📅 Schedule: Branch creation - "before 3am on Monday" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

â™» Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

This PR has been generated by Mend Renovate using a curated preset maintained by Sanity. View repository job log here

socket-security[bot] commented 7 months ago

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

Package New capabilities Transitives Size Publisher
npm/chalk@4.1.2 None +4 92.9 kB sindresorhus
npm/concurrently@8.2.0 environment, filesystem +2 7.07 MB gustavohenke
npm/discover-path@1.0.0 filesystem 0 11.2 kB rexxars
npm/email-validator@2.0.4 None 0 12.1 kB manishsaraan
npm/eslint-config-prettier@9.1.0 None 0 20.8 kB lydell
npm/eslint-config-sanity@7.1.2 None +1 57.5 kB sanity-io
npm/eslint-plugin-prettier@5.1.3 None 0 33.9 kB jounqin
npm/eslint-plugin-react-hooks@4.6.0 environment 0 118 kB gnoff
npm/eslint@8.57.0 environment, filesystem Transitive: eval, shell, unsafe +45 8.19 MB eslintbot
npm/execa@5.1.1 environment, shell Transitive: filesystem +2 90.9 kB sindresorhus
npm/fs-extra@11.2.0 None 0 54.9 kB ryanzim
npm/get-latest-version@5.1.0 None 0 8.23 kB rexxars
npm/git-remote-origin-url@3.1.0 Transitive: environment, filesystem +1 8.41 kB sindresorhus
npm/git-user-info@2.0.3 Transitive: filesystem +4 34.4 kB rexxars
npm/github-url-to-object@4.0.6 None 0 30.2 kB zeke

🚮 Removed packages: npm/eslint-config-prettier@8.10.0, npm/eslint-config-sanity@6.0.0, npm/prettier@2.8.8, npm/react@17.0.2, npm/typescript@4.9.5

View full report↗︎

socket-security[bot] commented 7 months ago

🚨 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 NoteSource
Install scripts npm/core-js@2.6.12
  • Install script: postinstall
  • Source: node -e "try{require('./postinstall')}catch(e){}"
Install scripts npm/fsevents@1.2.13
  • Install script: install
  • Source: node install.js
Install scripts npm/esbuild@0.20.2

View full report↗︎

Next steps

What is an install script?

Install scripts are run when the package is installed. The majority of malware in npm is hidden in install scripts.

Packages should not be running non-essential scripts during install and there are often solutions to problems people solve with install scripts that can be run at publish time instead.

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/core-js@2.6.12
  • @SocketSecurity ignore npm/fsevents@1.2.13
  • @SocketSecurity ignore npm/esbuild@0.20.2