@batoanng/types
[](https://www.npmjs.com/package/@batoanng/types) [](https://packagephobia.com/result?p=@batoanng/types)
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
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 0.5.3 | 0 / 6 | |
| 0.5.2 | 0 / 5 | |
| 0.5.1 | 0 / 5 | |
| 0.5.0 | 0 / 5 | |
| 0.3.0 | 0 / 5 | |
| 0.2.0 | 0 / 5 |
v0.5.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.