@types/chai
TypeScript definitions for chai
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 |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:chalk | AI (typosquat): @types/chai is the official DefinitelyTyped scoped package; Levenshtein match to chalk is a false positive. | ai | |
| typosquat | typosquat.levenshtein:hapi | AI (typosquat): @types/chai is the official DefinitelyTyped scoped package; Levenshtein match to hapi is a false positive. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 5.2.3 | 2 / 0 | |
| 5.2.2 | 1 / 0 | |
| 5.2.1 | 1 / 0 | |
| 5.2.0 | 1 / 0 | |
| 5.0.1 | 1 / 0 | |
| 5.0.0 | 0 / 0 | |
| 4.3.0 | 0 / 0 |
v5.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.