@universal-middleware/express
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 23 of 23)
| Version | Deps | Published |
|---|---|---|
| 0.4.31 | 2 / 15 | |
| 0.4.30 | 2 / 14 | |
| 0.4.29 | 2 / 14 | |
| 0.4.28 | 2 / 14 | |
| 0.4.27 | 2 / 14 | |
| 0.4.26 | 2 / 14 | |
| 0.4.25 | 1 / 14 | |
| 0.4.24 | 1 / 14 | |
| 0.4.23 | 1 / 14 | |
| 0.4.22 | 1 / 14 | |
| 0.4.21 | 1 / 14 | |
| 0.4.20 | 1 / 14 | |
| 0.4.19 | 1 / 14 | |
| 0.4.18 | 1 / 14 | |
| 0.4.17 | 1 / 14 | |
| 0.4.16 | 1 / 14 | |
| 0.2.4 | 1 / 13 | |
| 0.2.3 | 1 / 11 | |
| 0.2.2 | 1 / 11 | |
| 0.2.1 | 1 / 11 | |
| 0.2.0 | 1 / 11 | |
| 0.1.1 | 1 / 10 | |
| 0.1.0 | 0 / 13 |
v0.4.31
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.2
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.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.