@types/joi
Stub TypeScript definitions entry for joi, which provides its own types definitions
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:koa | AI (typosquat): @types/joi is a legitimate DefinitelyTyped stub; Levenshtein match to 'koa' is a false positive. | ai | |
| typosquat | typosquat.levenshtein:got | AI (typosquat): @types/joi is a legitimate DefinitelyTyped stub; Levenshtein match to 'got' is a false positive. | ai | |
| typosquat | typosquat.levenshtein:zod | AI (typosquat): @types/joi is a legitimate DefinitelyTyped stub; Levenshtein match to 'zod' is a false positive. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Type stub packages are intentionally tiny with minimal metadata; this is expected for DefinitelyTyped stubs. | ai | |
| phantom-deps | phantom-dep:joi | AI (phantom-deps): Stub package depends on joi for its types; no direct import needed by design. | ai |
Versions (showing 4 of 4)
| Version | Deps | Published |
|---|---|---|
| 17.2.3 | 1 / 0 | |
| 17.2.2 | 1 / 0 | |
| 17.2.1 | 1 / 0 | |
| 17.2.0 | 1 / 0 |
v17.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.