@tanstack/router-cli@1.167.34
Modern and scalable routing for React applications
AI Security Review
scanned 1mo ago · by lpm-firewall-aiThe scanner's dependency-bridge signal is explained by normal delegation to @tanstack/router-generator. Source inspection found no lifecycle execution, credential collection, network code, shell execution, or persistence.
Decision evidence
public snapshot- No install lifecycle hook is declared; scripts are development and build tasks.
- The CLI entry point only exposes explicit generate and watch commands.
- Generation delegates to the matching TanStack router generator dependency.
- The watch command monitors configured route files and regenerates output after the user starts it.
- README includes a passive tracking image, but package code does not request it.
Source & flagged code
5 flagged · loading sourcePackage metadata claims a different repository identity while copied source loads a runtime dependency bridge.
dist/cjs/generate.cjsView on unpkg · L1Generation delegates to the matching TanStack router generator dependency.
dist/cjs/generate.cjsView on unpkg · L1Findings
Affected versions and remediation
This report applies to @tanstack/router-cli@1.167.34.
See all versions of @tanstack/router-cli for other recorded verdicts.
- Review the evidence and your use of @tanstack/router-cli@1.167.34 before allowing it. Restrict the permissions described in this report.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.