@activepieces/piece-google-contacts@0.5.3
AI Security Review
scanned 20d ago · by lpm-firewall-aiThe scanner’s cloud metadata and command execution signals are consistent with bundled Google authentication support. The exported custom API action has a separate, user-triggered TLS verification side effect that presents unresolved risk, so a warning is appropriate.
Decision evidence
public snapshot- The manifest points to src/index.js and declares no dependencies or lifecycle scripts.
- The generic API action accepts a URL from its input and sends the request through a shared client.
- That action is included in the exported Google Contacts actions.
- The request client changes Node’s TLS verification setting to disabled when sending a request.
- The TLS override is reached through a user-invoked API action; the source does not establish hidden credential transfer or an install-time attack.
Source & flagged code
5 flaggedA single source file combines environment access, network access, and code or shell execution; review context before blocking.
src/index.jsView on unpkg · L37Findings
Affected versions and remediation
This report applies to @activepieces/piece-google-contacts@0.5.3.
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.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.