registry / @activepieces/piece-google-contacts / 0.5.5
@activepieces/piece-google-contacts@0.5.5
AI Security Review
scanned 11d ago · by lpm-firewall-aiThe manifest has no lifecycle scripts, and the exported piece performs Google Contacts operations against the intended Google API. Scanner flags for shell execution and metadata access match bundled authentication support code, not a demonstrated package attack.
Static reason
One or more suspicious static signals were detected.
Trigger
A workflow invokes a contact action or enables or runs the polling trigger.
Impact
No malicious impact was established; the visible account changes are contact operations invoked by the workflow.
Mechanism
Contact requests use the Google People API and the connected account’s bearer token; the reviewed source shows no package lifecycle hook.
AI rationale
The manifest has no lifecycle scripts, and the exported piece performs Google Contacts operations against the intended Google API. Scanner flags for shell execution and metadata access match bundled authentication support code, not a demonstrated package attack.
Evidence
package.jsonsrc/index.js
Network endpoints1
people.googleapis.com/v1
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 points to src/index.js and declares no lifecycle scripts or package dependencies.
- The bundle exports the Google Contacts piece; its piece-specific behavior defines contact actions and a polling trigger.
- The contact API helper targets people.googleapis.com, and the add-contact action sends caller-provided contact fields using the connected account’s bearer token.
- The flagged command execution appears in a bundled pluggable-auth helper; the cloud metadata addresses appear in Google metadata support code.
Evidence against
Behavioral surface
ChildProcessCryptoEnvironmentVarsEvalFilesystemNetworkShell
HighEntropyStringsMinifiedPossibleObfuscationUrlStrings
NoLicense
Source & flagged code
5 flaggedsrc/index.jsView file
48${h}
L49: `+await t.crypto.sha256DigestHex(m),S=await K2(t.crypto,t.securityCredentials.secretAccessKey,s,t.region,o),E=await Wu(t.crypto,S,_),T=`${GN} Credential=${t.securityCredentials.acc...
L50: To learn more about authentication and Google APIs, visit:
High
37`+S+"}":"{"+E.join(",")+"}",o=S,h}}a(l,"str"),typeof Wk.stringify!="function"&&(Wk.stringify=function(p,f,y){var m;if(o="",n="",typeof y=="number")for(m=0;m<y;m+=1)n+=" ";else type...
L38: `,r:"\r",t:" "},i,s=a(function(S){throw{name:"SyntaxError",message:S,at:r,text:i}},"error"),u=a(function(S){return S&&S!==o&&s("Expected '"+S+"' instead of '"+o+"'"),o=i.charAt(r),...
L39: Supported algorithms are:
...
L48: ${h}
L49: `+await t.crypto.sha256DigestHex(m),S=await K2(t.crypto,t.securityCredentials.secretAccessKey,s,t.region,o),E=await Wu(t.crypto,S,_),T=`${GN} Credential=${t.securityCredentials.acc...
L50: To learn more about authentication and Google APIs, visit:
High
Same File Env Network Execution
A single source file combines environment access, network access, and code or shell execution; review context before blocking.
src/index.jsView on unpkg · L3737
Findings
6 High3 Medium5 Low
HighChild Processsrc/index.js
HighShell
HighSame File Env Network Executionsrc/index.js
HighCommand Output Exfiltrationsrc/index.js
HighCloud Metadata Accesssrc/index.js
HighTrigger Reachable Command Output Exfiltrationsrc/index.js
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
LowEval
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
LowNo License
Affected versions and remediation
This report applies to @activepieces/piece-google-contacts@0.5.5.
See all versions of @activepieces/piece-google-contacts for other recorded verdicts.
- Review the evidence and your use of @activepieces/piece-google-contacts@0.5.5 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.