@tinkoff/module-loader-client
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
Versions (showing 18 of 18)
| Version | Deps | Published |
|---|---|---|
| 0.9.1 | 2 / 0 | |
| 0.8.4 | 2 / 0 | |
| 0.8.3 | 2 / 0 | |
| 0.8.2 | 2 / 0 | |
| 0.8.1 | 2 / 0 | |
| 0.7.9 | 2 / 0 | |
| 0.7.8 | 2 / 0 | |
| 0.7.7 | 2 / 0 | |
| 0.7.6 | 2 / 0 | |
| 0.7.5 | 2 / 0 | |
| 0.7.3 | 2 / 0 | |
| 0.7.2 | 2 / 0 | |
| 0.6.7 | 2 / 0 | |
| 0.6.6 | 2 / 0 | |
| 0.6.5 | 2 / 0 | |
| 0.6.3 | 2 / 0 | |
| 0.5.4 | 2 / 0 | |
| 0.5.3 | 2 / 0 |
v0.7.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.