@react-router/express
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@react-router/node | AI (dependencies): Same monorepo/release train as this package; versioned identically and maintained by remix-run. | ai |
Versions (showing 42 of 42)
| Version | Deps | Published |
|---|---|---|
| 8.3.0 | 1 / 9 | |
| 8.2.0 | 1 / 9 | |
| 8.1.0 | 1 / 9 | |
| 8.0.1 | 1 / 9 | |
| 8.0.0 | 1 / 9 | |
| 7.18.1 | 1 / 9 | |
| 7.18.0 | 1 / 9 | |
| 7.17.0 | 1 / 9 | |
| 7.16.0 | 1 / 9 | |
| 7.15.1 | 1 / 9 | |
| 7.15.0 | 1 / 9 | |
| 7.14.2 | 1 / 9 | |
| 7.14.1 | 1 / 9 | |
| 7.14.0 | 1 / 9 | |
| 7.13.2 | 1 / 9 | |
| 7.13.1 | 1 / 9 | |
| 7.13.0 | 1 / 9 | |
| 7.12.0 | 1 / 9 | |
| 7.11.0 | 1 / 9 | |
| 7.10.1 | 1 / 9 | |
| 7.10.0 | 1 / 9 | |
| 7.9.6 | 1 / 9 | |
| 7.9.5 | 1 / 9 | |
| 7.9.4 | 1 / 9 | |
| 7.9.3 | 1 / 9 | |
| 7.9.2 | 1 / 9 | |
| 7.9.1 | 1 / 9 | |
| 7.9.0 | 1 / 9 | |
| 7.8.2 | 1 / 9 | |
| 7.8.1 | 1 / 9 | |
| 7.8.0 | 1 / 9 | |
| 7.7.1 | 1 / 9 | |
| 7.7.0 | 1 / 9 | |
| 7.6.3 | 1 / 9 | |
| 7.6.2 | 1 / 9 | |
| 7.6.1 | 1 / 9 | |
| 7.6.0 | 1 / 9 | |
| 7.5.3 | 1 / 9 | |
| 7.5.2 | 1 / 9 | |
| 7.5.1 | 1 / 9 | |
| 7.5.0 | 1 / 9 | |
| 7.4.1 | 1 / 9 |
v8.3.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v8.2.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v8.1.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v7.18.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v7.15.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v7.15.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v7.14.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v7.14.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v7.14.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v7.10.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v7.9.6
2 findingsPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
This version was published by a different npm account (GitHub Actions) than the most recent previously approved version (mjackson) on 2025-11-13, but it carries Sigstore provenance attestation. This means the package moved to a trusted publisher (CI/CD with OIDC, e.g. GitHub Actions) — a supply-chain integrity improvement, not a compromise, since a stolen npm token cannot forge provenance bound to the source repository. Recorded as INFO for audit trail.
v7.6.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.5.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.4.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.