Skip to content

[Snyk] Security upgrade axios from 1.13.6 to 1.15.0#353

Open
sunil-lakshman wants to merge 1 commit intomainfrom
snyk-fix-11704530ffea183bbf18f672ad32761c
Open

[Snyk] Security upgrade axios from 1.13.6 to 1.15.0#353
sunil-lakshman wants to merge 1 commit intomainfrom
snyk-fix-11704530ffea183bbf18f672ad32761c

Conversation

@sunil-lakshman
Copy link
Copy Markdown
Contributor

snyk-top-banner

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

Snyk changed the following file(s):

  • package.json
  • package-lock.json

Vulnerabilities that will be fixed with an upgrade:

Issue Score
critical severity Unintended Proxy or Intermediary ('Confused Deputy')
SNYK-JS-AXIOS-15965856
  230  
high severity HTTP Response Splitting
SNYK-JS-AXIOS-15969258
  186  

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.

@sunil-lakshman sunil-lakshman requested a review from a team as a code owner April 11, 2026 07:08
@github-actions
Copy link
Copy Markdown

We regret to inform you that you are currently not able to merge your changes into the main branch due to restrictions applied by our SRE team. To proceed with merging your changes, we kindly request that you create a pull request from the development branch. Our team will then review the changes and work with you to ensure a successful merge into the main branch.

@github-actions
Copy link
Copy Markdown

🔒 Security Scan Results

ℹ️ Note: Only vulnerabilities with available fixes (upgrades or patches) are counted toward thresholds.

Check Type Count (with fixes) Without fixes Threshold Result
🔴 Critical Severity 0 0 10 ✅ Passed
🟠 High Severity 1 0 25 ✅ Passed
🟡 Medium Severity 1 0 500 ✅ Passed
🔵 Low Severity 0 0 1000 ✅ Passed

⏱️ SLA Breach Summary

✅ No SLA breaches detected. All vulnerabilities are within acceptable time thresholds.

Severity Breaches (with fixes) Breaches (no fixes) SLA Threshold (with/no fixes) Status
🔴 Critical 0 0 15 / 30 days ✅ Passed
🟠 High 0 0 30 / 120 days ✅ Passed
🟡 Medium 0 0 90 / 365 days ✅ Passed
🔵 Low 0 0 180 / 365 days ✅ Passed

✅ BUILD PASSED - All security checks passed

@github-actions
Copy link
Copy Markdown

Coverage report

St.
Category Percentage Covered / Total
🟢 Statements 99.32% 877/883
🟢 Branches 97.23% 281/289
🟢 Functions 97.95% 191/195
🟢 Lines 99.4% 832/837

Test suite run success

654 tests passing in 31 suites.

Report generated by 🧪jest coverage report action from 1f13782

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