@zapier/zapier-sdk
Complete Zapier SDK - combines all Zapier SDK packages
Supply chain provenance
Status for the latest visible version.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/index-eliz1Uq3.d.mts | AI (source-diff): TypeScript declaration file (.d.mts); long lines are generated type signatures, not obfuscated executable code. | ai | |
| source-diff | obfuscated-file:dist/index-eliz1Uq3.d.ts | AI (source-diff): TypeScript declaration file (.d.ts); long lines are generated type signatures, not obfuscated executable code. | ai | |
| source-diff | obfuscated-file:dist/index-DjQ4XDAV.d.mts | AI (source-diff): TypeScript declaration file (.d.mts) with long lines is normal bundled type output from tsup; not executable code. | ai | |
| source-diff | obfuscated-file:dist/index-DjQ4XDAV.d.ts | AI (source-diff): TypeScript declaration file (.d.ts) with long lines is normal bundled type output from tsup; not executable code. | ai | |
| source-diff | obfuscated-file:dist/index-Bfvj0KLi.d.ts | AI (source-diff): TypeScript declaration file with long lines is normal tsup bundle output, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/index-Bfvj0KLi.d.mts | AI (source-diff): TypeScript declaration file with long lines is normal tsup bundle output, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/index-3fBEDEsp.d.mts | AI (source-diff): TypeScript declaration files with long lines are normal bundled type output, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/index-3fBEDEsp.d.ts | AI (source-diff): TypeScript declaration files with long lines are normal bundled type output, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/index-4QyPPLfu.d.mts | AI (source-diff): TypeScript declaration bundle from tsup; long lines are normal for rolled-up type definitions, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/index-4QyPPLfu.d.ts | AI (source-diff): TypeScript declaration bundle from tsup; long lines are normal for rolled-up type definitions, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/index-SDDmBk2j.d.ts | AI (source-diff): Generated TypeScript declaration file; long lines are normal for bundled type exports, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/index-SDDmBk2j.d.mts | AI (source-diff): Generated TypeScript declaration file; long lines are normal for bundled type exports, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/index-CjP7lGzL.d.mts | AI (source-diff): Bundled TypeScript declaration file from tsup; long lines are type rollup artifacts, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/index-CjP7lGzL.d.ts | AI (source-diff): Same as .d.mts — tsup-generated type declaration bundle, not obfuscated code. | ai | |
| source-diff | obfuscated-file:dist/index-iKbnOz6r.d.ts | AI (source-diff): TypeScript declaration file with long lines from bundled type exports; not obfuscated code. | ai | |
| source-diff | obfuscated-file:dist/index-iKbnOz6r.d.mts | AI (source-diff): TypeScript declaration file with long lines from bundled type exports; not obfuscated code. | ai | |
| source-diff | obfuscated-file:dist/index-D2HKNk0N.d.ts | AI (source-diff): Same as above — bundled .d.ts declaration file with long lines is expected tsup output. | ai | |
| source-diff | obfuscated-file:dist/index-D2HKNk0N.d.mts | AI (source-diff): Bundled TypeScript declaration file; long lines are normal for tsup-generated type rollups, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/experimental.mjs | AI (source-diff): Standard tsup/rollup minified bundle output; sample shows readable code, not obfuscation. Stable pattern for this build-tool-generated package. | ai | |
| source-diff | obfuscated-file:dist/index-DcdtPei-.d.mts | AI (source-diff): Bundled TypeScript declaration file; long lines are normal tsup/rollup output, not obfuscation. | ai | |
| publish-pattern | rapid-publish | AI (publish-pattern): GitLab CI/CD automated publishing pipeline; rapid successive publishes are expected for this package. | ai | |
| source-diff | obfuscated-file:dist/index-DcdtPei-.d.ts | AI (source-diff): Bundled TypeScript declaration file; long lines are normal tsup/rollup output, not obfuscation. | ai | |
| phantom-deps | phantom-dep:@zapier/actions-sdk | AI (phantom-deps): Same-org dependency re-exported by umbrella package; not directly imported by design. | ai | |
| phantom-deps | phantom-dep:@zapier/shared-sdk | AI (phantom-deps): Same-org dependency re-exported by umbrella package; not directly imported by design. | ai | |
| provenance | publisher-changed | AI (provenance): New publisher jdeal_zapier and all new maintainers are Zapier-namespaced; consistent with internal team transition. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): New dep is @zapier/zapier-sdk-core, a first-party scoped package from the same org. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Removal paired with zapier-branded additions; consistent with internal rotation. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): New maintainers are zapier-branded accounts; consistent with internal team changes, not a hostile takeover. | ai | |
| phantom-deps | phantom-dep:@zapier/policy-schema | AI (phantom-deps): Same-org sibling dep declared in package.json; phantom-dep false positive for this monorepo umbrella package. | ai |
Versions (showing 51 of 151)
| Version | Deps | Published |
|---|---|---|
| 0.15.12 | 1 / 5 | |
| 0.15.11 | 1 / 5 | |
| 0.15.10 | 1 / 5 | |
| 0.15.9 | 1 / 5 | |
| 0.15.8 | 1 / 5 | |
| 0.15.4 | 1 / 5 | |
| 0.15.3 | 1 / 5 | |
| 0.15.2 | 1 / 5 | |
| 0.15.1 | 1 / 5 | |
| 0.15.0 | 1 / 5 | |
| 0.14.0 | 1 / 5 | |
| 0.13.9 | 1 / 5 | |
| 0.13.8 | 1 / 5 | |
| 0.13.7 | 1 / 5 | |
| 0.13.6 | 1 / 5 | |
| 0.13.5 | 1 / 5 | |
| 0.13.4 | 1 / 5 | |
| 0.13.3 | 1 / 5 | |
| 0.13.2 | 1 / 5 | |
| 0.13.1 | 1 / 5 | |
| 0.13.0 | 1 / 5 | |
| 0.12.1 | 1 / 5 | |
| 0.12.0 | 1 / 5 | |
| 0.11.2 | 1 / 5 | |
| 0.11.1 | 1 / 5 | |
| 0.11.0 | 1 / 5 | |
| 0.10.0 | 1 / 5 | |
| 0.9.0 | 1 / 5 | |
| 0.8.3 | 1 / 5 | |
| 0.8.2 | 1 / 5 | |
| 0.8.1 | 1 / 5 | |
| 0.8.0 | 1 / 5 | |
| 0.6.4 | 1 / 5 | |
| 0.6.3 | 1 / 5 | |
| 0.6.2 | 1 / 5 | |
| 0.6.1 | 1 / 5 | |
| 0.6.0 | 1 / 5 | |
| 0.5.2 | 1 / 5 | |
| 0.5.1 | 1 / 5 | |
| 0.5.0 | 1 / 5 | |
| 0.4.1 | 2 / 4 | |
| 0.4.0 | 2 / 4 | |
| 0.3.1 | 4 / 3 | |
| 0.3.0 | 4 / 3 | |
| 0.2.1 | 4 / 3 | |
| 0.2.0 | 2 / 2 | |
| 0.1.1 | 4 / 2 | |
| 0.1.0 | 4 / 2 | |
| 0.0.3 | 4 / 2 | |
| 0.0.2 | 4 / 2 | |
| 0.0.1 | 2 / 2 |
v0.15.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.