@types/webassembly-js-api
Stub TypeScript definitions entry for typescript, 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 — 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 |
|---|---|---|---|---|
| publish-pattern | new-deps-added | AI (publish-pattern): The new dep (webassembly-js-api) is a phantom/declarative dep in a stub @types package with no executable code; not an attack vector here. | ai | |
| npm-metadata | suspicious-initial-version | AI (npm-metadata): @types/* packages from DefinitelyTyped routinely use 0.0.0 as their version; this is a well-established convention for the types publisher, not a malware indicator. | ai | |
| bogus-package | bogus-package | AI (bogus-package): This is an intentional stub @types/ package with no code — tiny payload and minimal README are expected by design, not spam indicators. | ai | |
| phantom-deps | phantom-dep:webassembly-js-api | AI (phantom-deps): Stub @types/ packages declare a dep on the underlying package for type resolution without importing it; phantom-dep is a stable false positive for this package. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 2.0.0 | 1 / 0 | |
| 0.0.3 | 0 / 0 | |
| 0.0.2 | 0 / 0 | |
| 0.0.1 | 0 / 0 | |
| 0.0.0 | 0 / 0 |
v0.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.