@remix-run/headers
A toolkit for working with HTTP headers in JavaScript
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 0.21.1 | 0 / 4 | |
| 0.21.0 | 0 / 4 | |
| 0.20.0 | 0 / 4 | |
| 0.19.0 | 0 / 2 | |
| 0.18.0 | 0 / 2 | |
| 0.17.2 | 0 / 2 | |
| 0.17.1 | 0 / 2 | |
| 0.17.0 | 0 / 2 | |
| 0.16.0 | 0 / 2 | |
| 0.15.0 | 0 / 2 | |
| 0.14.0 | 0 / 2 | |
| 0.13.0 | 0 / 2 | |
| 0.12.0 | 0 / 2 |
v0.21.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.21.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.20.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.19.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.