bare-http1
Supply chain provenance
Status for the latest visible version.
Maintainers
Versions (showing 23 of 23)
| Version | Deps | Published |
|---|---|---|
| 4.5.6 | 4 / 6 | |
| 4.5.5 | 4 / 5 | |
| 4.5.4 | 4 / 5 | |
| 4.5.3 | 4 / 5 | |
| 4.5.2 | 4 / 5 | |
| 4.5.1 | 4 / 5 | |
| 4.4.0 | 4 / 5 | |
| 4.3.1 | 4 / 5 | |
| 4.3.0 | 4 / 5 | |
| 4.2.4 | 4 / 5 | |
| 4.2.3 | 4 / 5 | |
| 4.2.2 | 4 / 5 | |
| 4.2.1 | 4 / 5 | |
| 4.2.0 | 4 / 5 | |
| 4.1.6 | 4 / 5 | |
| 4.1.5 | 4 / 5 | |
| 4.1.4 | 4 / 5 | |
| 4.1.3 | 4 / 5 | |
| 4.1.2 | 4 / 5 | |
| 4.1.1 | 3 / 5 | |
| 4.1.0 | 3 / 5 | |
| 4.0.4 | 3 / 5 | |
| 4.0.3 | 3 / 5 |
v4.5.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.5.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.5.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.5.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.