@zapier/zapier-sdk@0.102.3
Complete Zapier SDK - combines all Zapier SDK packages
AI Security Review
scanned 19d ago · by lpm-firewall-aiThe manifest has no install hook, and the flagged process launch belongs to an explicitly invoked browser-opening helper. Runtime telemetry is associated with the SDK’s Zapier tracking behavior; the inspected sources do not establish a concrete attack.
Decision evidence
public snapshot- package.json has no install lifecycle hook; its scripts are build, clean, rebuild, dev, typecheck, and test.
- The command execution code opens a validated HTTP(S) URL in the system browser and is reached only when the URL-opening helper is called.
- Runtime telemetry defaults to Zapier tracking and can be disabled or redirected through SDK options or environment configuration.
- Both CommonJS and ESM bundles contain the corresponding SDK runtime, with no inspected evidence of an attack.
Source & flagged code
5 flaggedThis package version adds a dangerous source file absent from the previous stored version; route for source-aware review.
dist/chunk-GQP5NSYD.cjsView on unpkgSource combines command execution, command-output handling, and outbound requests; review data flow before blocking.
dist/chunk-GQP5NSYD.cjsView on unpkg · L11Findings
Affected versions and remediation
This report applies to @zapier/zapier-sdk@0.102.3.
See all versions of @zapier/zapier-sdk for other recorded verdicts.
- Review the evidence and your use of @zapier/zapier-sdk@0.102.3 before allowing it. Restrict the permissions described in this report.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.