Skip to content

[Snyk] Security upgrade @openapitools/openapi-generator-cli from 2.17.0 to 2.23.2#16

Closed
jimmyn wants to merge 1 commit intomasterfrom
snyk-fix-ae642e0aebf352092f286abcc4a1e629
Closed

[Snyk] Security upgrade @openapitools/openapi-generator-cli from 2.17.0 to 2.23.2#16
jimmyn wants to merge 1 commit intomasterfrom
snyk-fix-ae642e0aebf352092f286abcc4a1e629

Conversation

@jimmyn
Copy link
Copy Markdown
Collaborator

@jimmyn jimmyn commented Sep 26, 2025

snyk-top-banner

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

Snyk changed the following file(s):

  • 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:

Issue Score
medium severity Allocation of Resources Without Limits or Throttling
SNYK-JS-AXIOS-12613773
  738  

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:

🦉 Allocation of Resources Without Limits or Throttling

The following vulnerabilities are fixed with an upgrade:
- https://snyk.io/vuln/SNYK-JS-AXIOS-12613773
@socket-security
Copy link
Copy Markdown

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff Package Supply Chain
Security
Vulnerability Quality Maintenance License
Addedhttps-proxy-agent@​7.0.41001009179100
Addedagent-base@​7.1.11001009180100
Addedsocks-proxy-agent@​8.0.3991008481100
Updatedsocks@​2.8.4 ⏵ 2.8.310010010083100
Updated@​openapitools/​openapi-generator-cli@​2.17.0 ⏵ 2.23.49210010097 -1100

View full report

Copy link
Copy Markdown

@chatgpt-codex-connector chatgpt-codex-connector bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Comment thread package.json
Comment on lines 71 to 75
"@commitlint/cli": "^19.8.0",
"@commitlint/config-conventional": "^19.8.0",
"@eslint/js": "^9.22.0",
"@openapitools/openapi-generator-cli": "^2.17.0",
"@openapitools/openapi-generator-cli": "^2.23.2",
"@release-it/conventional-changelog": "^10.0.0",
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

[P1] Update yarn.lock alongside package.json upgrade

The dependency bump only changes package.json while yarn.lock remains untouched. With Yarn, the lock file dictates the installed version, so anyone running yarn install will still pull @openapitools/openapi-generator-cli@2.17.0 and the reported vulnerability will persist. Please regenerate yarn.lock (or otherwise ensure the lock pins 2.23.2) so the upgrade actually takes effect.

Useful? React with 👍 / 👎.

@jimmyn jimmyn closed this Dec 2, 2025
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