Skip to content

[Snyk] Security upgrade axios from 1.13.1 to 1.13.5 #141

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.

Sign up for GitHub

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

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

[Snyk] Security upgrade axios from 1.13.1 to 1.13.5 #141

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -176,7 +176,7 @@
"@noble/curves": "^2.0.1",
"@types/localtunnel": "^2.0.4",
"agent0-sdk": "0.2.1",
"axios": "^1.12.2",
"axios": "^1.13.5",

@chatgpt-codex-connector chatgpt-codex-connector Bot Feb 11, 2026

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 Badge Update pnpm-lock.yaml alongside axios bump

This change updates only package.json, but the lockfile still pins axios to 1.13.1 with the old specifier (pnpm-lock.yaml lines 48-50), so reproducible installs will not pick up 1.13.5; additionally, workflows that run pnpm install --frozen-lockfile (e.g. .github/workflows/pr-checks.yml lines 27/50 and .github/workflows/publish.yml line 159) will fail because the lockfile is out of sync with package.json. Please regenerate and commit pnpm-lock.yaml with this dependency bump.

Useful? React with 👍 / 👎.

@gemini-code-assist gemini-code-assist Bot Feb 11, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

critical

While upgrading axios is the correct step to fix the security vulnerability, the pnpm-lock.yaml file has not been updated to reflect this change. As noted in the PR description, this needs to be done manually. Without updating the lock file, the vulnerable version of axios might still be installed, leaving the project exposed.

Please run the following command and commit the updated lock file:

pnpm install

"bignumber.js": "^9.3.1",
"buffer": "^6.0.3",
"chalk": "^5.4.1",
Expand Down
Loading