@twurple/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): @twurple/chat is a Twitch SDK package; Levenshtein match to 'chalk' is a false positive. | ai | |
| phantom-deps | phantom-dep:@d-fischer/deprecate | AI (phantom-deps): Declared utility dep used indirectly via decorators/config; stable false positive for this package. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 8.1.4 | 9 / 1 | |
| 8.1.3 | 9 / 1 | |
| 8.1.2 | 9 / 1 | |
| 8.1.1 | 9 / 1 | |
| 8.1.0 | 9 / 1 | |
| 8.0.3 | 9 / 1 | |
| 8.0.2 | 9 / 1 | |
| 8.0.1 | 9 / 1 | |
| 8.0.0 | 9 / 1 |
v8.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.