← Home

@zapier/zapier-sdk-cli

npm Repository Homepage

Command line interface for Zapier SDK

19
Versions
SEE LICENSE IN LICENSE
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

zapier-engineering

Keywords

zapierclisdk

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Transition from individual jdeal_zapier to org account zapier-engineering; consistent with Zapier's publishing consolidation. ai
publish-pattern new-deps-added AI (publish-pattern): New deps are established packages (conf, cross-keychain, proper-lockfile) replacing a removed internal dep; consistent with a credential-handling refactor. ai
dependencies unvetted-dep:handlebars AI (dependencies): Handlebars is a standard templating dep for a CLI scaffolding tool; stable across versions. ai
dependencies unvetted-dep:@zapier/zapier-sdk-cli-login AI (dependencies): First-party Zapier scoped package; expected dependency for this CLI. ai
phantom-deps phantom-dep:cli-table3 AI (phantom-deps): cli-table3 is a declared dependency used transitively; phantom-dep heuristic false positive for this CLI package. ai
phantom-deps phantom-dep:jsonwebtoken AI (phantom-deps): jsonwebtoken is a declared dependency for OAuth/JWT flows; phantom-dep heuristic false positive for this CLI package. ai

Versions (showing 19 of 19)

Version Deps Published
0.52.12 24 / 8
0.52.10 24 / 8
0.43.1 22 / 8
0.41.1 20 / 7
0.41.0 20 / 7
0.38.2 20 / 7
0.38.1 20 / 7
0.38.0 20 / 7
0.23.1 19 / 7
0.5.0 14 / 7
0.4.1 12 / 7
0.4.0 12 / 7
0.3.1 11 / 6
0.2.1 11 / 6
0.2.0 12 / 6
0.1.1 7 / 4
0.1.0 7 / 4
0.0.3 7 / 4
0.0.2 7 / 4

v0.52.12

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.52.10

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.43.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.41.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.38.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.38.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.38.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.23.1

2 findings
HIGH Publisher changed: jdeal_zapier → zapier-engineering (on 2026-02-04) provenance

This version was published by a different npm account than previous versions on 2026-02-04. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.5.0

2 findings
HIGH Publisher changed: jdeal_zapier → zapier-engineering (on 2025-08-29) provenance

This version was published by a different npm account than previous versions on 2025-08-29. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.4.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.4.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.3

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.