@izara_project/izara-core-library-asynchronous-flow
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 40 of 40)
| Version | Deps | Published |
|---|---|---|
| 1.0.43 | 0 / 7 | |
| 1.0.42 | 0 / 7 | |
| 1.0.41 | 0 / 7 | |
| 1.0.40 | 0 / 7 | |
| 1.0.39 | 0 / 7 | |
| 1.0.38 | 0 / 10 | |
| 1.0.37 | 0 / 8 | |
| 1.0.36 | 0 / 8 | |
| 1.0.35 | 0 / 8 | |
| 1.0.34 | 0 / 8 | |
| 1.0.33 | 0 / 8 | |
| 1.0.32 | 0 / 1 | |
| 1.0.31 | 1 / 1 | |
| 1.0.30 | 1 / 1 | |
| 1.0.29 | 1 / 1 | |
| 1.0.28 | 0 / 1 | |
| 1.0.27 | 0 / 1 | |
| 1.0.25 | 0 / 1 | |
| 1.0.24 | 0 / 1 | |
| 1.0.23 | 5 / 1 | |
| 1.0.22 | 5 / 1 | |
| 1.0.21 | 5 / 1 | |
| 1.0.20 | 5 / 1 | |
| 1.0.19 | 5 / 1 | |
| 1.0.18 | 5 / 1 | |
| 1.0.17 | 5 / 1 | |
| 1.0.16 | 5 / 1 | |
| 1.0.15 | 5 / 1 | |
| 1.0.14 | 5 / 1 | |
| 1.0.13 | 5 / 1 | |
| 1.0.12 | 5 / 1 | |
| 1.0.11 | 5 / 1 | |
| 1.0.10 | 5 / 1 | |
| 1.0.9 | 5 / 1 | |
| 1.0.8 | 5 / 1 | |
| 1.0.7 | 5 / 1 | |
| 1.0.6 | 5 / 1 | |
| 1.0.5 | 5 / 1 | |
| 1.0.4 | 5 / 1 | |
| 1.0.3 | 6 / 1 |
v1.0.43
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.42
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.41
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.40
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.39
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.38
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.