@remix-run/session-middleware
Middleware for managing sessions with cookie-based storage
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 |
|---|---|---|---|---|
| maintainer-change | maintainer-removed | AI (maintainer-change): Remix-run org package published via GitHub Actions CI/CD; individual maintainer removal is expected and not a takeover signal. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): New deps are all first-party @remix-run/* packages; expected for a session-middleware package in the remix monorepo. | ai | |
| npm-metadata | suspicious-initial-version | AI (npm-metadata): 0.0.0 is a standard initial release pattern in the Remix monorepo by the core team maintainer. | ai | |
| dependencies | unvetted-dep:@remix-run/cookie | AI (dependencies): First-party sibling package in the remix-run org; not a third-party risk. | ai |
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 0.3.3 | 3 / 8 | |
| 0.3.2 | 3 / 8 | |
| 0.3.1 | 3 / 8 | |
| 0.3.0 | 3 / 8 | |
| 0.2.2 | 3 / 8 | |
| 0.2.1 | 3 / 8 | |
| 0.2.0 | 3 / 6 | |
| 0.1.4 | 3 / 6 | |
| 0.1.3 | 3 / 6 | |
| 0.1.2 | 3 / 6 | |
| 0.1.1 | 0 / 7 | |
| 0.1.0 | 0 / 6 | |
| 0.0.0 | 0 / 6 |
v0.3.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.3.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.3.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.3.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.2.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.2.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.2.0
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.