@remix-run/compression-middleware
Middleware for compressing HTTP responses
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| npm-metadata | suspicious-initial-version | AI (npm-metadata): @remix-run scoped monorepo package from trusted publisher; 0.0.0 is a standard placeholder version in this ecosystem. | ai | |
| provenance | slsa-provenance | AI (provenance): Official remix-run monorepo CI publishing; SLSA attestation is expected for all versions. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Remix-run org uses GitHub Actions as publisher; individual maintainer removal is expected org practice. | ai | |
| dependencies | unvetted-dep:@remix-run/mime | AI (dependencies): First-party @remix-run scoped sibling package from the same org/repo; not a third-party risk. | ai | |
| dependencies | unvetted-dep:@remix-run/response | AI (dependencies): First-party @remix-run scoped sibling package from the same org/repo; not a third-party risk. | ai |
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 0.1.11 | 3 / 7 | |
| 0.1.10 | 3 / 7 | |
| 0.1.9 | 3 / 7 | |
| 0.1.8 | 3 / 7 | |
| 0.1.7 | 3 / 7 | |
| 0.1.6 | 3 / 7 | |
| 0.1.5 | 3 / 7 | |
| 0.1.4 | 3 / 5 | |
| 0.1.3 | 3 / 5 | |
| 0.1.2 | 3 / 5 | |
| 0.1.1 | 3 / 5 | |
| 0.1.0 | 0 / 5 | |
| 0.0.0 | 0 / 5 |
v0.1.11
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.1.10
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.1.9
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.1.8
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.1.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.1.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.1.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.1.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.1.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.1.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.1.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.1.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.