Repository navigation
Zapier: platform-core 19.3.0, run the CLI through npx - #3
Merged
Merged
Conversation
zapier-platform-cli pinned vulnerable tar, simple-git, sigstore and yeoman packages (49 advisories, 3 critical) even in 19.3.0. It only runs on a developer machine, so it is no longer a dev dependency; npm run validate and the publish steps call it through npx.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
Take the remaining security fixes, including releases younger than 7 days. A follow-up to #2.
Zapier
zapier-platform-corezapier-platform-cli(dev)npxzapier-platform-clicarried 49 advisories, 3 of them critical (tarhardlink path traversal,simple-gitunsafe-operation guard). Version 19.3.0 still pins the same vulnerable versions throughyeoman-environment>fly-import>@npmcli/arborist. npm's "fix available" hint for 19.3.0 was wrong.The CLI only runs on a developer machine, for
validate,pushandpromote, and nothing from it ships to Zapier. So it is no longer a dev dependency:The README's publish steps now use
npx -p zapier-platform-cli zapier-platform ....Note
npm auditinzapier/now reports 0 findings, down from 52.npm testpasses (6 tests).npm run validateshows the same single warning as before (D003, connection label).Not changed
Warning
zodfindings stay. They are fixed only in zod 4.6.6, and everyn8n-workflowrelease, including the 2.47.0 beta, depends on zod 3.n8n-workflowis a dev dependency used for types. At runtime the node uses the n8n install's own copy, so thiszodnever ships. The node stays on stable 2.46.minimatchfindings underopenapi-typescript7.13.0, the latest version. It is codegen tooling that reads only our own spec.Java (Jackson 2.22.4), .NET, PHP and Python are already on their latest patched versions. The
js/lockfile picks up one in-range update.Spec sync
The live spec now marks response objects with
"additionalProperties": false. That comes from thehono-openapi1.5.0 update in simulieren/hscode-sveltekit#114. Request bodies are unchanged andjs/src/schema.tsgenerates the same types. The commit syncsopenapi.jsonsospec-driftpasses.