Skip to content

[Snyk] Upgrade @contentstack/delivery-sdk from 4.11.0 to 4.11.1#43

Open
harshithad0703 wants to merge 1 commit intomainfrom
snyk-upgrade-ed72be5a1c65c56cd21062717e929896
Open

[Snyk] Upgrade @contentstack/delivery-sdk from 4.11.0 to 4.11.1#43
harshithad0703 wants to merge 1 commit intomainfrom
snyk-upgrade-ed72be5a1c65c56cd21062717e929896

Conversation

@harshithad0703
Copy link
Contributor

snyk-top-banner

Snyk has created this PR to upgrade @contentstack/delivery-sdk from 4.11.0 to 4.11.1.

ℹ️ 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 1 version ahead of your current version.

  • The recommended version was released 22 days ago.

Issues fixed by the recommended upgrade:

Issue Score Exploit Maturity
high severity Prototype Pollution
SNYK-JS-AXIOS-15252993
169 Proof of Concept
medium severity Prototype Pollution
SNYK-JS-LODASH-15053838
169 No Known Exploit

Important

  • Check the changes in this PR to ensure they won't cause issues with your project.
  • This PR was automatically created by Snyk using the credentials of a real user.
  • Max score is 1000. Note that the real score may have changed since the PR was raised.

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:

Snyk has created this PR to upgrade @contentstack/delivery-sdk from 4.11.0 to 4.11.1.

See this package in npm:
@contentstack/delivery-sdk

See this project in Snyk:
https://app.snyk.io/org/contentstack-devex/project/315ec182-1897-4975-b529-26fed99398b6?utm_source=github&utm_medium=referral&page=upgrade-pr
@harshithad0703 harshithad0703 requested a review from a team as a code owner March 3, 2026 06:42
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