@activepieces/piece-google-contacts@0.5.4
AI Security Review
scanned 27d ago · by lpm-firewall-aiThe entrypoint contains an active transport behavior that disables TLS verification, creating a concrete security risk for HTTPS requests. The inspected source does not establish malicious exfiltration or an attacker-controlled destination.
Decision evidence
public snapshot- The entrypoint’s HTTP send method sets NODE_TLS_REJECT_UNAUTHORIZED to 0 before issuing requests, disabling TLS certificate verification for Node.js HTTPS connections.
- The package exposes Google Contacts actions that use its bundled API client, so the unsafe transport behavior is relevant to the package’s runtime.
- The manifest points to src/index.js and declares no lifecycle scripts or dependencies.
- The package’s described integration is Google Contacts, with contact operations using the People API.
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.4.
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.4 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.