@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 |
|---|---|---|
| 1.1.0 | 2 / 5 | |
| 1.0.3 | 2 / 5 | |
| 1.0.2 | 2 / 5 | |
| 1.0.0 | 2 / 5 | |
| 0.64.0 | 4 / 4 | |
| 0.63.0 | 4 / 4 | |
| 0.62.0 | 4 / 4 | |
| 0.61.0 | 4 / 4 | |
| 0.60.0 | 4 / 4 | |
| 0.59.0 | 4 / 4 | |
| 0.58.0 | 4 / 4 | |
| 0.57.0 | 4 / 4 | |
| 0.56.2 | 4 / 4 | |
| 0.56.1 | 4 / 4 | |
| 0.56.0 | 4 / 4 | |
| 0.55.0 | 4 / 4 | |
| 0.54.1 | 4 / 4 | |
| 0.54.0 | 4 / 4 | |
| 0.53.0 | 4 / 4 | |
| 0.52.0 | 4 / 4 | |
| 0.51.0 | 4 / 4 | |
| 0.50.0 | 4 / 4 | |
| 0.49.0 | 4 / 4 | |
| 0.48.1 | 4 / 4 | |
| 0.48.0 | 4 / 4 | |
| 0.47.1 | 4 / 4 | |
| 0.47.0 | 4 / 4 | |
| 0.46.1 | 4 / 4 | |
| 0.46.0 | 4 / 4 | |
| 0.45.2 | 4 / 5 | |
| 0.45.1 | 4 / 5 | |
| 0.45.0 | 4 / 5 | |
| 0.44.0 | 4 / 5 | |
| 0.43.0 | 4 / 5 | |
| 0.42.1 | 2 / 5 | |
| 0.42.0 | 2 / 5 | |
| 0.41.2 | 2 / 5 | |
| 0.41.1 | 2 / 5 | |
| 0.41.0 | 2 / 5 | |
| 0.40.4 | 2 / 5 | |
| 0.40.3 | 2 / 5 | |
| 0.40.2 | 2 / 5 | |
| 0.40.1 | 2 / 5 | |
| 0.40.0 | 2 / 5 | |
| 0.39.1 | 2 / 5 | |
| 0.39.0 | 2 / 5 | |
| 0.38.0 | 2 / 5 | |
| 0.37.0 | 2 / 5 | |
| 0.36.0 | 2 / 5 | |
| 0.35.0 | 2 / 5 | |
| 0.34.1 | 2 / 5 |
v1.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.64.0
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.63.0
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.62.0
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.61.0
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.60.0
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.59.0
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.58.0
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.57.0
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.56.2
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.56.1
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.56.0
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.55.0
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.54.1
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.54.0
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.53.0
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.52.0
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.51.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.50.0
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.49.0
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.48.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.48.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.47.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.47.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.46.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.46.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.45.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.45.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.45.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.44.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.42.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.42.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.41.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.41.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.41.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.40.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.40.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.40.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.40.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.40.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.39.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.39.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.38.0
2 findingsThis version was published by a different npm account than previous versions on 2026-03-27. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.37.0
2 findingsThis version was published by a different npm account than previous versions on 2026-03-25. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.36.0
2 findingsThis version was published by a different npm account than previous versions on 2026-03-20. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.35.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.34.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.