SWI-3723 [Snyk] Security upgrade zapier-platform-core from 15.5.1 to 18.5.0

[bwappsec]

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

Snyk changed the following file(s):

• samples/client/petstore/zapier/package.json

Vulnerabilities that will be fixed with an upgrade:

	Issue	Score
	Arbitrary Code Injection SNYK-JS-LODASH-15869625	180
	Prototype Pollution SNYK-JS-LODASH-15869619	87

Breaking Change Risk

Notice: This assessment is enhanced by AI.

---

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:

🦉 Prototype Pollution
🦉 Arbitrary Code Injection

[bwappsec]

This is a major version upgrade from 15.5.1 to 18.5.0, which includes significant breaking changes across versions 17.x and 18.x. Developer action is required to ensure compatibility.

v18.0.0 Breaking Changes:

• Node.js Runtime: The platform now runs on Node.js 22. This is a major environment change that could affect dependencies.
• Throttling Middleware: A new throwForThrottling middleware has been added. This is a breaking change if your app uses afterResponse middleware to handle 429 (throttling) errors.
• Schema Flag Change: The experimental skipCleanArrayInputData flag has been replaced with cleanInputData. This is only a breaking change if you were using the experimental flag.

v17.0.0 Breaking Changes:

• Schema Separation: This is the most impactful change. Authentication, input, and output fields have been split into separate, stricter schemas.
• Removed Field Types: Several field types and properties have been removed from schemas. For example, code, file, integer, and text are no longer supported in AuthenticationSchema.fields. Using these will cause a validation error.
• ES Module Support: You can now use modern ES Module syntax (import/export), which may require changes to your project's configuration (e.g., "type": "module" in package.json).

Recommendation: This upgrade requires significant developer action. You must review your integration's schema definitions for authentication, inputFields, and outputFields to ensure they comply with the new, stricter schemas in v17. Use the zapier validate command to identify and fix any unsupported field types or properties. Additionally, verify your app's compatibility with the Node.js 22 runtime.

Source: v18.0.0 Release Notes, v17.0.0 Release Notes

Notice 🤖: This content was augmented using artificial intelligence. AI-generated content may contain errors and should be reviewed for accuracy before use.

[bwappsec]

✅ Snyk checks have passed. No issues have been found so far.

Status	Scan Engine	Critical	High	Medium	Low	Total (0)
✅	Open Source Security	0	0	0	0	0 issues
✅	Licenses	0	0	0	0	0 issues
✅	Code Security	0	0	0	0	0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.