@googleapis/chat
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:chalk | AI (typosquat): @googleapis/chat is Google's official scoped package for the Chat API; the Levenshtein match to 'chalk' is purely coincidental and not a typosquat. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 45.0.0 | 1 / 8 | |
| 44.7.0 | 1 / 8 | |
| 44.6.0 | 1 / 8 | |
| 44.5.0 | 1 / 8 | |
| 44.4.0 | 1 / 8 | |
| 44.3.1 | 1 / 8 | |
| 44.3.0 | 1 / 8 | |
| 44.2.0 | 1 / 8 | |
| 44.1.0 | 1 / 8 |
v45.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v44.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v44.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v44.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v44.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v44.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.