@websolutespa/bom-core
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 47 of 47)
| Version | Deps | Published |
|---|---|---|
| 3.0.1 | 1 / 12 | |
| 3.0.0 | 1 / 12 | |
| 2.0.1 | 1 / 10 | |
| 2.0.0 | 1 / 10 | |
| 1.8.24 | 1 / 10 | |
| 1.8.23 | 1 / 10 | |
| 1.8.22 | 1 / 10 | |
| 1.8.21 | 1 / 10 | |
| 1.8.20 | 1 / 10 | |
| 1.8.19 | 1 / 10 | |
| 1.8.18 | 1 / 10 | |
| 1.8.17 | 1 / 10 | |
| 1.8.16 | 1 / 10 | |
| 1.8.15 | 1 / 10 | |
| 1.8.14 | 1 / 10 | |
| 1.8.13 | 1 / 10 | |
| 1.8.12 | 1 / 10 | |
| 1.8.11 | 1 / 10 | |
| 1.8.10 | 1 / 10 | |
| 1.8.9 | 1 / 10 | |
| 1.8.8 | 1 / 10 | |
| 1.8.7 | 1 / 10 | |
| 1.8.6 | 1 / 10 | |
| 1.8.5 | 1 / 10 | |
| 1.8.4 | 1 / 10 | |
| 1.8.3 | 1 / 10 | |
| 1.8.2 | 1 / 10 | |
| 1.8.1 | 1 / 10 | |
| 1.8.0 | 1 / 10 | |
| 1.7.16 | 1 / 10 | |
| 1.7.15 | 1 / 10 | |
| 1.7.14 | 1 / 10 | |
| 1.7.13 | 1 / 10 | |
| 1.7.12 | 1 / 10 | |
| 1.7.11 | 1 / 10 | |
| 1.7.10 | 1 / 10 | |
| 1.7.9 | 1 / 10 | |
| 1.7.8 | 1 / 10 | |
| 1.7.7 | 1 / 10 | |
| 1.7.6 | 1 / 10 | |
| 1.7.5 | 1 / 10 | |
| 1.7.4 | 1 / 10 | |
| 1.7.3 | 1 / 10 | |
| 1.7.2 | 1 / 10 | |
| 1.7.1 | 1 / 10 | |
| 1.7.0 | 1 / 10 | |
| 1.6.0 | 1 / 10 |
v2.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.