@activepieces/piece-google-bigquery@0.1.2
AI Security Review
scanned 27d ago · by lpm-firewall-aiThe entrypoint is a Google BigQuery integration, but its bundled HTTP client disables TLS verification process-wide before requests. This is a concrete security risk warranting a warning; the inspected source does not establish malicious behavior.
Decision evidence
public snapshot- The manifest loads the bundled entrypoint, which defines Google BigQuery actions and triggers.
- The bundled HTTP client sets Node.js TLS certificate verification to disabled before sending requests.
- The entrypoint uses Google authentication to build bearer authorization for the piece's actions.
- The manifest declares no lifecycle scripts or dependencies.
- The executable-authentication code is part of the bundled Google authentication library; inspected code shows no package-specific command execution path.
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-bigquery@0.1.2.
See all versions of @activepieces/piece-google-bigquery for other recorded verdicts.
- Review the evidence and your use of @activepieces/piece-google-bigquery@0.1.2 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.