@tanstack/react-router
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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): TanStack/router migrated to GitHub Actions CI/CD publishing with SLSA provenance attestation — this is an improvement in supply chain security, not a risk. Stable for this package. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): lachlancollins is a known TanStack contributor; addition is consistent with legitimate team growth for this well-established project. | ai | |
| dependencies | unvetted-dep:@tanstack/history | AI (dependencies): First-party TanStack sibling package from the same monorepo (TanStack/router). Expected dependency; not a security concern. | ai | |
| dependencies | unvetted-dep:@tanstack/react-store | AI (dependencies): First-party TanStack package from the same ecosystem. Expected dependency for @tanstack/react-router; not a security concern. | ai | |
| dependencies | unvetted-dep:@tanstack/router-core | AI (dependencies): First-party TanStack sibling package from the same monorepo (TanStack/router). Expected core dependency; not a security concern. | ai |
Versions (showing 32 of 732)
| Version | Deps | Published |
|---|---|---|
| 1.32.2 | 4 / 6 | |
| 1.32.0 | 4 / 6 | |
| 1.31.29 | 4 / 6 | |
| 1.31.28 | 4 / 6 | |
| 1.31.27 | 4 / 6 | |
| 1.31.26 | 4 / 6 | |
| 1.31.25 | 4 / 6 | |
| 1.31.24 | 4 / 6 | |
| 1.31.23 | 4 / 6 | |
| 1.31.22 | 4 / 6 | |
| 1.31.21 | 4 / 6 | |
| 1.31.20 | 4 / 6 | |
| 1.31.19 | 4 / 6 | |
| 1.31.17 | 4 / 6 | |
| 1.31.16 | 4 / 6 | |
| 1.31.15 | 4 / 6 | |
| 1.31.14 | 4 / 6 | |
| 1.31.13 | 4 / 6 | |
| 1.31.12 | 4 / 6 | |
| 1.31.11 | 4 / 6 | |
| 1.31.10 | 4 / 6 | |
| 1.31.9 | 4 / 6 | |
| 1.31.8 | 4 / 6 | |
| 1.31.7 | 4 / 6 | |
| 1.31.6 | 4 / 6 | |
| 1.31.5 | 4 / 6 | |
| 1.31.4 | 4 / 6 | |
| 1.31.3 | 4 / 6 | |
| 1.31.2 | 4 / 6 | |
| 1.31.1 | 4 / 6 | |
| 1.31.0 | 4 / 6 | |
| 1.30.1 | 4 / 6 |
v1.32.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.32.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.31.29
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.31.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.31.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.31.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.31.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.31.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.31.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.31.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.31.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.31.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.31.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.31.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.31.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.31.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.31.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.31.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.31.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.31.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.31.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.31.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.31.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.31.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.31.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.31.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.31.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.31.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.31.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.31.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.31.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.30.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.