@zapier/zapier-sdk@0.119.0
Complete Zapier SDK - combines all Zapier SDK packages
AI Security Review
scanned 4d ago · by lpm-firewall-aiThe package's default runtime telemetry sends account-identifying context and potentially local stack details to its tracking service, but the README does not disclose that behavior. This is a telemetry concern rather than evidence of credential theft or malicious account actions.
Decision evidence
public snapshot- Event emission is enabled by default when the SDK is created.
- The default transport posts event properties to a Zapier tracking endpoint; environment variables or SDK options can change the transport or endpoint.
- Telemetry context can include user and account IDs extracted from the Zapier auth token.
- Unhandled exception events include error messages and stack traces.
- The manifest has no install, preinstall, or postinstall lifecycle hook.
- The README describes a trackingBaseUrl option, consistent with the tracking endpoint serving the SDK's purpose.
Source & flagged code
4 flaggedSource combines command execution, command-output handling, and outbound requests; review data flow before blocking.
dist/chunk-6FKWG6WZ.mjsView on unpkg · L11Package contains a possible secret pattern.
dist/chunk-6FKWG6WZ.mjsView on unpkg · L8293Findings
Affected versions and remediation
This report applies to @zapier/zapier-sdk@0.119.0.
See all versions of @zapier/zapier-sdk for other recorded verdicts.
- Review the evidence and your use of @zapier/zapier-sdk@0.119.0 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.