@tanstack/start-server-core
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): TanStack publishes via GitHub Actions CI; individual maintainer list changes are expected org hygiene, not takeover signals. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): fetchdts is a legitimate TS utility dep; package has SLSA provenance and strong ecosystem trust. | ai | |
| dependencies | unvetted-dep:fetchdts | AI (dependencies): fetchdts is a type-fetching utility with no runtime execution risk; TanStack publisher context makes supply-chain concern low. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): lachlancollins is a known TanStack contributor; adding maintainers to a major ecosystem project is routine. | ai | |
| provenance | publisher-changed | AI (provenance): Transition from personal npm publish (tannerlinsley) to GitHub Actions CI/CD with SLSA provenance. This is the expected modern publishing pattern for TanStack packages. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Package has 417 versions, 5.7M weekly downloads, and SLSA provenance. Dormancy signal is a false positive for this actively maintained TanStack sub-package. | ai | |
| dependencies | unvetted-dep:h3-v2 | AI (dependencies): h3-v2 is a deliberate npm alias for [email protected], a known HTTP framework used intentionally by TanStack Start. This aliasing pattern is stable for this package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): TanStack packages intentionally have minimal READMEs pointing to tanstack.com docs. This is a stable pattern across all TanStack packages, not a spam/phishing indicator. | ai |
Versions (showing 51 of 181)
| Version | Deps | Published |
|---|---|---|
| 1.168.1 | 7 / 4 | |
| 1.168.0 | 7 / 4 | |
| 1.167.30 | 7 / 4 | |
| 1.167.29 | 7 / 4 | |
| 1.167.28 | 7 / 5 | |
| 1.167.27 | 7 / 5 | |
| 1.167.26 | 6 / 6 | |
| 1.167.24 | 6 / 6 | |
| 1.167.23 | 6 / 6 | |
| 1.167.22 | 6 / 6 | |
| 1.167.21 | 6 / 6 | |
| 1.167.20 | 6 / 6 | |
| 1.167.4 | 6 / 6 | |
| 1.148.0 | 7 / 3 | |
| 1.146.0 | 7 / 3 | |
| 1.142.13 | 7 / 3 | |
| 1.140.1 | 7 / 3 | |
| 1.139.14 | 7 / 3 | |
| 1.139.12 | 7 / 3 | |
| 1.139.10 | 7 / 3 | |
| 1.139.8 | 7 / 3 | |
| 1.139.7 | 7 / 3 | |
| 1.139.6 | 7 / 3 | |
| 1.139.4 | 7 / 3 | |
| 1.139.3 | 7 / 3 | |
| 1.139.2 | 7 / 3 | |
| 1.139.0 | 7 / 3 | |
| 1.136.17 | 7 / 3 | |
| 1.136.16 | 7 / 3 | |
| 1.136.15 | 7 / 3 | |
| 1.136.13 | 7 / 3 | |
| 1.136.11 | 7 / 3 | |
| 1.136.9 | 7 / 3 | |
| 1.136.8 | 7 / 3 | |
| 1.136.5 | 7 / 3 | |
| 1.136.4 | 7 / 3 | |
| 1.136.3 | 7 / 3 | |
| 1.136.2 | 7 / 3 | |
| 1.136.1 | 7 / 3 | |
| 1.135.2 | 7 / 3 | |
| 1.134.20 | 7 / 3 | |
| 1.134.18 | 7 / 3 | |
| 1.134.15 | 7 / 3 | |
| 1.134.12 | 7 / 3 | |
| 1.134.10 | 7 / 3 | |
| 1.134.9 | 7 / 3 | |
| 1.134.5 | 7 / 3 | |
| 1.134.4 | 7 / 3 | |
| 1.133.35 | 7 / 3 | |
| 1.133.31 | 7 / 3 | |
| 1.132.41 | 7 / 3 |
v1.168.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.168.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.167.30
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.167.29
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.167.28
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.167.27
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.167.26
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.167.24
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.167.23
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.167.21
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.167.20
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.167.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.148.0
2 findingsThis version was published by a different npm account than previous versions on 2026-01-11. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.146.0
2 findingsThis version was published by a different npm account than previous versions on 2026-01-08. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.142.13
2 findingsThis version was published by a different npm account than previous versions on 2025-12-23. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.140.1
2 findingsThis version was published by a different npm account than previous versions on 2025-12-09. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.139.14
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.139.12
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.139.10
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.139.8
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.139.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.139.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.139.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.139.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.139.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.139.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.136.17
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.136.16
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.136.15
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.136.13
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.136.11
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.136.9
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.136.8
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.136.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.136.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.136.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.136.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.136.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.135.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.134.20
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.134.18
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.134.15
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.134.12
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.134.10
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.134.9
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.134.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.134.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.133.35
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.133.31
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.