registry / @zapier/zapier-sdk / 0.110.1
@zapier/zapier-sdk@0.110.1
Complete Zapier SDK - combines all Zapier SDK packages
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThe scanner findings are explained by normal SDK features: authenticated API access, telemetry, and approval-browser handling. Source inspection found no lifecycle trigger or concrete malicious behavior.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
A consumer creates and uses the SDK, such as making an authenticated API request or handling an approval.
Impact
No unconsented installation-time execution, persistence, credential theft, or unrelated exfiltration was established.
Mechanism
Authenticated Zapier API calls, optional telemetry, and approval URL opening.
AI rationale
The scanner findings are explained by normal SDK features: authenticated API access, telemetry, and approval-browser handling. Source inspection found no lifecycle trigger or concrete malicious behavior.
Decision evidence
public snapshotAI called this Clean at 96.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The manifest has no install lifecycle hook; its scripts are build, development, typecheck, and test commands.
- The CJS bundle dynamically loads child_process only for a validated HTTP(S) URL opener.
- The ESM bundle has the same constrained browser-opening helper.
- Telemetry can post events, but its default endpoint is the package-aligned Zapier tracking API.
Evidence against
- No preinstall, install, postinstall, or prepare script, self-dependency, eval, shell execution, credential harvesting, or import-time payload was found.
- The process launch uses fixed platform URL-opening commands and rejects non-HTTP(S) URLs.
- Credential and network code implements the SDK's explicit authenticated API and OAuth flows; no unrelated exfiltration endpoint was found.
Behavioral surface
ChildProcessEnvironmentVarsFilesystemNetwork
HighEntropyStringsMinifiedUrlStrings
Source & flagged code
5 flaggeddist/chunk-IRHF55YK.mjsView file
2805async function loadChildProcess() {
L2806: return import(`${nodePrefix}child_process`);
L2807: }
High
Child Process
Package source references child process execution.
dist/chunk-IRHF55YK.mjsView on unpkg · L280511// src/constants.ts
L12: var ZAPIER_BASE_URL = globalThis.process?.env?.ZAPIER_BASE_URL || "https://zapier.com";
L13: function getZapierSdkService() {
...
L69: function getZapierDefaultApprovalMode() {
L70: const isInteractive = !!globalThis.process?.stdin?.isTTY && !!globalThis.process?.stdout?.isTTY;
L71: return isInteractive ? "poll" : "throw";
...
L557: }
L558: const base64UrlPattern = /^[A-Za-z0-9_-]+$/;
L559: return parts.every((part) => part.length > 0 && base64UrlPattern.test(part));
...
L759: headers: censorHeaders(options2?.headers),
L760: body: options2?.body && typeof options2.body === "string" ? (() => {
L761: try {
High
Command Output Exfiltration
Source combines command execution, command-output handling, and outbound requests; review data flow before blocking.
dist/chunk-IRHF55YK.mjsView on unpkg · L118004patternName = generic_password
severity = medium
line = 8004
Findings
1 Critical2 High4 Medium5 Low
CriticalPrevious Version Dangerous Deltadist/chunk-BURXHBSW.cjs
HighChild Processdist/chunk-IRHF55YK.mjs
HighCommand Output Exfiltrationdist/chunk-IRHF55YK.mjs
MediumSecret Patterndist/chunk-IRHF55YK.mjs
MediumNetwork
MediumEnvironment Vars
MediumSecret Patterndist/chunk-BURXHBSW.cjs
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
LowNo License
Affected versions and remediation
This report applies to @zapier/zapier-sdk@0.110.1.
See all versions of @zapier/zapier-sdk for other recorded verdicts.
- Review the evidence and your use of @zapier/zapier-sdk@0.110.1 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.