@zapier/zapier-sdk@0.107.0
Complete Zapier SDK - combines all Zapier SDK packages
AI Security Review
scanned 19d ago · by lpm-firewall-aiSource inspection found no install hook or concrete attack behavior. The flagged process and network operations are used for validated browser opening and SDK telemetry, and do not establish malicious activity.
Decision evidence
public snapshot- The manifest points consumers to the SDK bundles and lists no install lifecycle hook.
- The child-process helper accepts only HTTP or HTTPS URLs and uses platform browser-opening commands.
- Telemetry sends event data to a tracking endpoint derived from Zapier configuration; the inspected auth context extracts user and account identifiers rather than forwarding the token.
- The experimental declaration files contain type declarations and imports, not executable behavior.
- Scanner flags for command execution and outbound requests map to a browser-opening helper and configurable SDK telemetry, not a demonstrated attack chain.
- Telemetry can be disabled or sent to console through environment configuration; its event transport does not itself establish credential exfiltration.
Source & flagged code
5 flaggedPackage source references child process execution.
dist/chunk-XGSFXI2W.mjsView on unpkg · L2691Source combines command execution, command-output handling, and outbound requests; review data flow before blocking.
dist/chunk-XGSFXI2W.mjsView on unpkg · L10Findings
Affected versions and remediation
This report applies to @zapier/zapier-sdk@0.107.0.
See all versions of @zapier/zapier-sdk for other recorded verdicts.
- Review the evidence and your use of @zapier/zapier-sdk@0.107.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.