Skip to content

[Snyk] Upgrade axios from 1.4.0 to 1.6.3#3

Open
naiba4 wants to merge 1 commit intomainfrom
snyk-upgrade-2fdf9ff2796d90056e74dde43a56645e
Open

[Snyk] Upgrade axios from 1.4.0 to 1.6.3#3
naiba4 wants to merge 1 commit intomainfrom
snyk-upgrade-2fdf9ff2796d90056e74dde43a56645e

Conversation

@naiba4
Copy link
Owner

@naiba4 naiba4 commented Jan 24, 2024

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


Snyk has created this PR to upgrade axios from 1.4.0 to 1.6.3.

ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

  • The recommended version is 6 versions ahead of your current version.
  • The recommended version was released a month ago, on 2023-12-26.

The recommended version fixes:

Severity Issue PriorityScore (*) Exploit Maturity
Cross-site Request Forgery (CSRF)
SNYK-JS-AXIOS-6032459		 676/1000
Why? Proof of Concept exploit, Has a fix available, CVSS 7.1		 Proof of Concept
Regular Expression Denial of Service (ReDoS)
SNYK-JS-AXIOS-6124857		 676/1000
Why? Proof of Concept exploit, Has a fix available, CVSS 7.1		 Proof of Concept

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

Release notes
Package name: axios from axios GitHub release notes
Commit messages
Package name: axios
  • b15b918 chore(release): v1.6.3 (#6151)
  • b76cce0 chore(ci): added branches filter for notify action; (#6084)
  • 5e7ad38 fix: Regular Expression Denial of Service (ReDoS) (#6132)
  • 8befb86 docs: update alloy link (#6145)
  • d18f40d docs: add headline sponsors
  • b3be365 chore(release): v1.6.2 (#6082)
  • 8739acb chore(ci): removed redundant release action; (#6081)
  • bfa9c30 chore(docs): fix outdated grunt to npm scripts (#6073)
  • a2b0fb3 chore(docs): update README.md (#6048)
  • b12a608 chore(ci): removed paths-ignore filter; (#6080)
  • 0c9d886 chore(ci): reworked ignoring files logic; (#6079)
  • 30873ee chore(ci): add paths-ignore config to testing action; (#6078)
  • cff9967 feat(withXSRFToken): added withXSRFToken option as a workaround to achieve the old `withCredentials` behavior; (#6046)
  • 7009715 chore(ci): fixed release notification action; (#6064)
  • 7144f10 chore(ci): fixed release notification action; (#6063)
  • f6d2cf9 chore(ci): fix publish action content permission; (#6061)
  • a22f4b9 chore(release): v1.6.1 (#6060)
  • cb8bb2b chore(ci): Publish to NPM with provenance (#5835)
  • 37cbf92 chore(ci): added labeling and notification for published PRs; (#6059)
  • dd465ab fix(formdata): fixed content-type header normalization for non-standard browser environments; (#6056)
  • 3dc8369 fix(platform): fixed emulated browser detection in node.js environment; (#6055)
  • f7adacd chore(release): v1.6.0 (#6031)
  • 9917e67 chore(ci): fix release-it arg; (#6032)
  • 96ee232 fix(CSRF): fixed CSRF vulnerability CVE-2023-45857 (#6028)

Compare

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.

For more information:

🧐 View latest project report

🛠 Adjust upgrade PR settings

🔕 Ignore this dependency or unsubscribe from future upgrade PRs

@pull-request-quantifier-deprecated
Copy link

pull-request-quantifier-deprecated bot commented Jan 24, 2024

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

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.

@guardrails
Copy link

guardrails bot commented Jan 24, 2024

⚠️ We detected 8 security issues in this pull request:

Vulnerable Libraries (8)
Severity Details
Medium pkg:npm/eslint-plugin-vue@9.8.0 (t) upgrade to: > 9.8.0
High pkg:npm/docsearch.js@2.6.3 (t) upgrade to: > 2.6.3
High pkg:npm/vuepress@2.0.0-beta.59 (t) upgrade to: > 2.0.0-beta.59
Medium pkg:npm/eslint@8.29.0 (t) upgrade to: > 8.29.0
High pkg:npm/vuepress-plugin-md-enhance@2.0.0-beta.143 (t) upgrade to: > 2.0.0-beta.143
Medium pkg:npm/@typescript-eslint/parser@5.46.1 (t) upgrade to: > 5.46.1
High pkg:npm/axios@1.6.3 upgrade to: > 1.6.3
Medium pkg:npm/@typescript-eslint/eslint-plugin@5.46.1 (t) upgrade to: > 5.46.1

More info on how to fix Vulnerable Libraries in JavaScript.

👉 Go to the dashboard for detailed results.

📥 Happy? Share your feedback with us.

@socket-security
Copy link

socket-security bot commented Jan 24, 2024

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

Package New capabilities Transitives Size Publisher
npm/@sentry/browser@7.95.0 network +7 9.77 MB sentry-bot
npm/axios@1.6.3 network Transitive: environment, filesystem +8 2.17 MB jasonsaayman

🚮 Removed packages: npm/@sentry/browser@7.36.0, npm/axios@1.4.0

View full report↗︎

@socket-security
Copy link

socket-security bot commented Jan 24, 2024

🚨 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
Network access npm/@sentry/utils@7.95.0
Unpublished package npm/@sentry-internal/tracing@7.95.0
  • Version: Invalid Date
Unpublished package npm/@sentry-internal/feedback@7.95.0
  • Version: Invalid Date
Unpublished package npm/@sentry-internal/replay-canvas@7.95.0
  • Version: Invalid Date
Unpublished package npm/@sentry/replay@7.95.0
  • Version: Invalid Date

View full report↗︎

Next steps

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 are unpublished packages?

Package version was not found on the registry. It may exist on a different registry and need to be configured to pull from that registry.

Packages can be removed from the registry by manually un-publishing, a security issue removal, or may simply never have been published to the registry. Reliance on these packages will cause problem when they are not found.

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/@sentry/utils@7.95.0
  • @SocketSecurity ignore npm/@sentry-internal/tracing@7.95.0
  • @SocketSecurity ignore npm/@sentry-internal/feedback@7.95.0
  • @SocketSecurity ignore npm/@sentry-internal/replay-canvas@7.95.0
  • @SocketSecurity ignore npm/@sentry/replay@7.95.0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

Extra Small

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@naiba4 @snyk-bot