All @tanstack/react-router versions
@tanstack/react-router @1.169.8+gfinternaltest.1lw2753
Keywords
Dependencies (4)
| Package | Constraint | Registry Status |
|---|---|---|
| isbot | ^5.1.22 | auto_approved |
| @tanstack/history | 1.161.6 | auto_approved |
| @tanstack/react-store | ^0.9.3 | auto_approved |
| @tanstack/router-core | 1.169.2 | auto_approved |
Dev Dependencies (10)
| Package | Constraint | Registry Status |
|---|---|---|
| zod | ^3.24.2 | auto_approved |
| vite | * | auto_approved |
| react | ^19.0.0 | auto_approved |
| combinate | ^1.1.11 | Not imported |
| react-dom | ^19.0.0 | auto_approved |
| vibe-rules | ^0.2.57 | pending |
| @types/node | >=20 | auto_approved |
| @vitejs/plugin-react | ^4.3.4 | auto_approved |
| @testing-library/react | ^16.2.0 | auto_approved |
| @testing-library/jest-dom | ^6.6.3 | auto_approved |
Transitive Dependency Tree
Changes from v1.169.2
No metadata changes detected.
File Changes
Risk Dispositions (3 applicable to this version, 0 other)
Accepted rules are downgraded to INFO on future analyses; rejected rules escalate to CRITICAL.
| Rule | Source | Disposition | Author | Reason | |
|---|---|---|---|---|---|
regressed-provenance |
provenance | reject | AI | AI (provenance): Provenance regression on a high-profile package with unknown publisher is a strong compromise signal. | |
obfuscated-file:router_init.js |
source-diff | reject | AI | AI (source-diff): 2.3MB obfuscated file with hex-mangled identifiers is not legitimate build output for this package. | |
url-dep:@tanstack/setup |
npm-metadata | reject | AI | AI (npm-metadata): SHA-pinned GitHub optionalDep bypasses registry; matches known attack vector for this namespace. |
SAST Findings (4)
Dependency '@tanstack/setup' in `optionalDependencies` points to 'github:tanstack/router#79ac49eedf774dd4b0cfa308722bc463cfe5885c' instead of a registry version. URL dependencies bypass the registry and can be swapped at any time. A 40-character commit SHA in a dependency URL is a strong supply-chain signal — the 2026-05-11 TanStack/Mini Shai-Hulud attack used this exact shape in `optionalDependencies` to smuggle a malicious payload past lifecycle-script and OSV checks.
This version was published without provenance, but prior versions were published via CI/CD with attestations. This is a strong signal of a potential account compromise or unauthorized publish. The axios attack (March 2026) exhibited exactly this pattern.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package tarball is not signed by the npm registry. This is unusual for packages published after 2023.
Review Summary
Risk score: 85. Findings: 3 high (+75), 1 medium (+10).