[Snyk] Security upgrade semantic-release from 19.0.2 to 22.0.0

[naiba4]

This PR was automatically created by Snyk using the credentials of a real user.

Snyk has created this PR to fix one or more vulnerable packages in the `yarn` dependencies of this project.

Changes included in this PR

• Changes to the following files to upgrade the vulnerable dependencies to a fixed version:
  • package.json

Note for zero-installs users

If you are using the Yarn feature zero-installs that was introduced in Yarn V2, note that this PR does not update the .yarn/cache/ directory meaning this code cannot be pulled and immediately developed on as one would expect for a zero-install project - you will need to run yarn to update the contents of the ./yarn/cache directory.
If you are not using zero-install you can ignore this as your flow should likely be unchanged.

⚠️ Warning

Failed to update the yarn.lock, please update manually before merging.

Vulnerabilities that will be fixed

With an upgrade:

Severity	Priority Score (*)	Issue	Breaking Change	Exploit Maturity
	220/1000 Why? Confidentiality impact: High, Integrity impact: Low, Availability impact: Low, Scope: Unchanged, Exploit Maturity: Proof of Concept, User Interaction (UI): None, Privileges Required (PR): None, Attack Complexity: Low, Attack Vector: Network, EPSS: 0.00043, Social Trends: No, Days since published: 0, Reachable: No, Transitive dependency: Yes, Is Malicious: No, Business Criticality: High, Provider Urgency: High, Package Popularity Score: 99, Impact: 7.84, Likelihood: 2.81, Score Version: V5	Server-side Request Forgery (SSRF) SNYK-JS-IP-6240864	Yes	Proof of Concept

(*) Note that the real score may have changed since the PR was raised.

Check the changes in this PR to ensure they won't cause issues with your project.

---

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

🛠 Adjust project settings

📚 Read more about Snyk's upgrade and patch logic

---

Learn how to fix vulnerabilities with free interactive lessons:

🦉 Server-side Request Forgery (SSRF)

[pull-request-quantifier-deprecated]

This PR has 2 quantified lines of changes. In general, a change size of upto 200 lines is ideal for the best PR experience!

---

Quantification details

Label      : Extra Small
Size       : +1 -1
Percentile : 0.8%

Total files changed: 1

Change summary by file extension:
.json : +1 -1

Change counts above are quantified counts, based on the PullRequestQuantifier customizations.

Why proper sizing of changes matters

Optimal pull request sizes drive a better predictable PR flow as they strike a
balance between between PR complexity and PR review overhead. PRs within the
optimal size (typical small, or medium sized PRs) mean:

• Fast and predictable releases to production:
  • Optimal size changes are more likely to be reviewed faster with fewer
    iterations.
  • Similarity in low PR complexity drives similar review times.
• Review quality is likely higher as complexity is lower:
  • Bugs are more likely to be detected.
  • Code inconsistencies are more likely to be detected.
• Knowledge sharing is improved within the participants:
  • Small portions can be assimilated better.
• Better engineering practices are exercised:
  • Solving big problems by dividing them in well contained, smaller problems.
  • Exercising separation of concerns within the code changes.

What can I do to optimize my changes

• Use the PullRequestQuantifier to quantify your PR accurately
  • Create a context profile for your repo using the context generator
  • Exclude files that are not necessary to be reviewed or do not increase the review complexity. Example: Autogenerated code, docs, project IDE setting files, binaries, etc. Check out the Excluded section from your prquantifier.yaml context profile.
  • Understand your typical change complexity, drive towards the desired complexity by adjusting the label mapping in your prquantifier.yaml context profile.
  • Only use the labels that matter to you, see context specification to customize your prquantifier.yaml context profile.
• Change your engineering behaviors
  • For PRs that fall outside of the desired spectrum, review the details and check if:
    • Your PR could be split in smaller, self-contained PRs instead
    • Your PR only solves one particular issue. (For example, don't refactor and code new features in the same PR).

How to interpret the change counts in git diff output

• One line was added: +1 -0
• One line was deleted: +0 -1
• One line was modified: +1 -1 (git diff doesn't know about modified, it will
  interpret that line like one addition plus one deletion)
• Change percentiles: Change characteristics (addition, deletion, modification)
  of this PR in relation to all other PRs within the repository.

---

Was this comment helpful? 👍  :ok_hand:  :thumbsdown: (Email)
Customize PullRequestQuantifier for this repository.

[socket-security]

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

Package	New capabilities	Transitives	Size	Publisher
npm/@octokit/[email protected]	None	0	24.2 kB	octokitbot
npm/@octokit/[email protected]	Transitive: network	+12	5.02 MB	octokitbot
npm/@octokit/[email protected]	None	+3	4.78 MB	octokitbot
npm/@octokit/[email protected]	Transitive: network	+9	4.91 MB	octokitbot
npm/@octokit/[email protected]	None	0	4.45 MB	octokitbot
npm/@octokit/[email protected]	Transitive: network	+13	5.22 MB	octokitbot
npm/@octokit/[email protected]	None	+5	4.71 MB	octokitbot
npm/@octokit/[email protected]	network	+8	4.87 MB	octokitbot
npm/@octokit/[email protected]	None	+1	4.68 MB	octokitbot
npm/@semantic-release/[email protected]	Transitive: environment, eval, filesystem, network, shell, unsafe	+257	101 MB	semantic-release-bot
npm/@semantic-release/[email protected]	network Transitive: environment, eval, filesystem, shell, unsafe	+257	101 MB	semantic-release-bot
npm/@semantic-release/[email protected]	filesystem Transitive: environment, eval, network, shell, unsafe	+257	101 MB	semantic-release-bot
npm/@semantic-release/[email protected]	Transitive: environment, eval, filesystem, network, shell, unsafe	+257	101 MB	semantic-release-bot
npm/@sindresorhus/[email protected]	None	0	57.5 kB	sindresorhus
npm/[email protected]	filesystem Transitive: environment, eval	+11	5.44 MB	oss-bot
npm/[email protected]	None	0	7.92 kB	oss-bot
npm/[email protected]	None	+1	157 kB	sindresorhus
npm/[email protected]	environment Transitive: filesystem, shell	+8	124 kB	semantic-release-bot
npm/[email protected]	Transitive: environment	+1	39.8 kB	sindresorhus
npm/[email protected]	None	+1	8.05 kB	sindresorhus
npm/[email protected]	None	0	9.57 kB	sindresorhus
npm/[email protected]	Transitive: environment	+10	176 kB	sindresorhus
npm/[email protected]	Transitive: environment, filesystem	+39	6.82 MB	mikaelb
npm/[email protected]	None	0	914 kB	tonybrix
npm/[email protected]	None	0	93.6 kB	broofa
npm/[email protected]	None	+5	457 kB	omnidan
npm/[email protected]	None	0	25.7 kB	sindresorhus
npm/[email protected]	environment, filesystem, network, shell, unsafe	0	9.99 MB	gar
npm/[email protected]	None	0	5.94 kB	sindresorhus
npm/[email protected]	None	+1	29.1 kB	sindresorhus
npm/[email protected]	None	0	5.89 kB	sindresorhus
npm/[email protected]	environment, network Transitive: eval, filesystem, shell, unsafe	+257	101 MB	semantic-release-bot
npm/[email protected]	None	+3	123 kB	sindresorhus
npm/[email protected]	None	0	4.27 kB	sindresorhus
npm/[email protected]	environment	+1	14.5 kB	sindresorhus
npm/[email protected]	None	0	3.15 kB	sindresorhus
npm/[email protected]	None	+5	377 kB	sindresorhus
npm/[email protected]	None	0	4.74 kB	jonkoops

🚮 Removed packages: npm/@octokit/[email protected], npm/@octokit/[email protected], npm/@octokit/[email protected], npm/@octokit/[email protected], npm/@octokit/[email protected], npm/@octokit/[email protected], npm/@octokit/[email protected], npm/@octokit/[email protected], npm/@octokit/[email protected], npm/@semantic-release/[email protected], npm/@semantic-release/[email protected], npm/@semantic-release/[email protected], npm/@semantic-release/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected]

View full report↗︎

[socket-security]

🚨 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	Note	Source
Filesystem access	npm/[email protected]	Module: fs/promises Location: Package overview	package.json
New author	npm/[email protected]	New Author: npm-cli-ops Previous Author: lukekarrys	package.json
New author	npm/[email protected]	New Author: jonkoops Previous Author: jfromaniello	Source
New author	npm/[email protected]	New Author: ehmicky Previous Author: sindresorhus	package.json
Environment variable access	npm/[email protected]	Env Vars: Location: Package overview	Source
Filesystem access	npm/[email protected]	Module: fs/promises Location: Package overview	Source
Unmaintained	npm/[email protected]	Last Publish: 6/23/2016, 12:18:06 PM	package.json
Environment variable access	npm/[email protected]	Env Vars: WT_SESSION Location: Package overview	package.json
Environment variable access	npm/[email protected]	Env Vars: ConEmuTask Location: Package overview	package.json
Environment variable access	npm/[email protected]	Env Vars: TERM_PROGRAM Location: Package overview	package.json
Environment variable access	npm/[email protected]	Env Vars: TERM Location: Package overview	package.json
Environment variable access	npm/[email protected]	Env Vars: TERMINAL_EMULATOR Location: Package overview	package.json
Environment variable access	npm/[email protected]	Env Vars: TERMINUS_SUBLIME Location: Package overview	package.json
Deprecated	npm/[email protected]	Reason: Renamed to read-package-up	package.json
Dynamic require	npm/[email protected]	Location: Package overview	package.json
Filesystem access	npm/@semantic-release/[email protected]	Module: fs-extra Location: Package overview	Source
Network access	npm/@semantic-release/[email protected]	Module: http-proxy-agent Location: Package overview	Source
Network access	npm/@semantic-release/[email protected]	Module: https-proxy-agent Location: Package overview	Source
Dynamic require	npm/[email protected]	Location: Package overview	Source
Network access	npm/[email protected]	Module: net Location: Package overview	Source
Network access	npm/[email protected]	Module: tls Location: Package overview	Source
Filesystem access	npm/[email protected]	Module: fs/promises Location: Package overview	Source
Dynamic require	npm/[email protected]	Location: Package overview	Source
Environment variable access	npm/[email protected]	Env Vars: ACTIONS_ID_TOKEN_REQUEST_URL Location: Package overview	Source
Environment variable access	npm/[email protected]	Env Vars: ACTIONS_ID_TOKEN_REQUEST_TOKEN Location: Package overview	Source
Environment variable access	npm/[email protected]	Env Vars: SIGSTORE_ID_TOKEN Location: Package overview	Source
Environment variable access	npm/[email protected]	Env Vars: XDG_DATA_HOME Location: Package overview	Source
Network access	npm/[email protected]	Module: http Location: Package overview	Source
Network access	npm/[email protected]	Module: https Location: Package overview	Source
Environment variable access	npm/[email protected]	Env Vars: comspec Location: Package overview	Source
Non OSI license	npm/[email protected]	License: BlueOak-1.0.0	Source
Environment variable access	npm/[email protected]	Env Vars: MINIMATCH_TESTING_PLATFORM Location: Package overview	Source
Environment variable access	npm/[email protected]	Env Vars: NODE_GYP_NULL_LOGGER Location: Package overview	Source
Filesystem access	npm/[email protected]	Module: fs/promises Location: Package overview	Source
Environment variable access	npm/[email protected]	Env Vars: ISEXE_TEST_PLATFORM Location: Package overview	Source
Deprecated	npm/[email protected]	Reason: should have been major release. Use 7.0.0	Source

View full report↗︎

Next steps

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 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 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 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 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 dynamic require?

Dynamic require can indicate the package is performing dangerous or unsafe dynamic code execution.

Packages should avoid dynamic imports when possible. Audit the use of dynamic require to ensure it is not executing malicious or vulnerable code.

What is network access?

This module accesses the network.

Packages should remove all network access that is functionally unnecessary. Consumers should audit network access to ensure legitimate use.

What is a non OSI license?

(Experimental) Package has a non-OSI-approved license.

Consider the terms of the license for your given use case.

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/[email protected] or ignore all packages with @SocketSecurity ignore-all

• @SocketSecurity ignore npm/[email protected]
• @SocketSecurity ignore npm/[email protected]
• @SocketSecurity ignore npm/[email protected]
• @SocketSecurity ignore npm/[email protected]
• @SocketSecurity ignore npm/[email protected]
• @SocketSecurity ignore npm/[email protected]
• @SocketSecurity ignore npm/[email protected]
• @SocketSecurity ignore npm/[email protected]
• @SocketSecurity ignore npm/[email protected]
• @SocketSecurity ignore npm/[email protected]
• @SocketSecurity ignore npm/@semantic-release/[email protected]
• @SocketSecurity ignore npm/@semantic-release/[email protected]
• @SocketSecurity ignore npm/[email protected]
• @SocketSecurity ignore npm/[email protected]