@google-cloud/ces
Gemini Enterprise for Customer Experience API client for Node.js
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:jest | AI (typosquat): Legitimate @google-cloud scoped package; short suffix 'ces' coincidentally close to unrelated packages. | ai | |
| typosquat | typosquat.levenshtein:cors | AI (typosquat): Same as above — scoped Google Cloud package, not a typosquat of cors. | ai | |
| typosquat | typosquat.levenshtein:qs | AI (typosquat): Same as above — scoped Google Cloud package, not a typosquat of qs. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 0.7.0 | 1 / 14 | |
| 0.6.0 | 1 / 14 | |
| 0.5.0 | 1 / 14 | |
| 0.4.1 | 1 / 14 | |
| 0.4.0 | 1 / 15 | |
| 0.3.0 | 1 / 15 | |
| 0.2.0 | 1 / 15 | |
| 0.1.0 | 1 / 15 |
v0.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
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. Only ~12% of npm packages have provenance, so this is common but not ideal.