@bemedev/basifun
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
Keywords
Versions (showing 14 of 14)
| Version | Deps | Published |
|---|---|---|
| 0.5.3 | 1 / 36 | |
| 0.5.2 | 1 / 37 | |
| 0.5.1 | 1 / 37 | |
| 0.5.0 | 1 / 37 | |
| 0.3.4 | 1 / 37 | |
| 0.3.3 | 1 / 37 | |
| 0.3.2 | 1 / 37 | |
| 0.3.1 | 1 / 37 | |
| 0.3.0 | 1 / 37 | |
| 0.2.1 | 1 / 36 | |
| 0.2.0 | 1 / 36 | |
| 0.1.6 | 2 / 35 | |
| 0.1.5 | 1 / 36 | |
| 0.1.4 | 1 / 36 |
v0.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.