@activepieces/piece-google-vertexai
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:ms | AI (phantom-deps): Transitive dependency via google-auth-library; used indirectly. | ai | |
| phantom-deps | phantom-dep:ws | AI (phantom-deps): Transitive dependency; declared for indirect use. | ai | |
| semgrep | semgrep:base64-decode | AI (semgrep): Decodes AI-generated image data from API response to write a file; not a malicious payload pattern. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Scoped monorepo piece package; missing metadata is typical for this publisher's ecosystem. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Consistent with Activepieces monorepo piece packaging conventions. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 0.1.3 | 6 / 1 | |
| 0.1.2 | 70 / 1 | |
| 0.1.1 | 6 / 1 | |
| 0.1.0 | 6 / 1 | |
| 0.0.2 | 5 / 0 | |
| 0.0.1 | 5 / 0 |
v0.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.