@tanstack/create-start
Tanstack Start Builder
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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): TanStack org transitioned publishing to GitHub Actions CI with SLSA attestation; stable legitimate change. | ai | |
| provenance | missing-githead | AI (provenance): Absence of gitHead is consistent with the CI/CD pipeline change; SLSA attestation provides stronger commit traceability. | ai | |
| dependencies | unvetted-dep:@tanstack/cta-framework-react-cra | AI (dependencies): Co-versioned sibling package from same TanStack monorepo; not an independent third-party risk. | ai | |
| dependencies | unvetted-dep:@tanstack/cta-framework-solid | AI (dependencies): Co-versioned sibling package from same TanStack monorepo; not an independent third-party risk. | ai | |
| dependencies | unvetted-dep:@tanstack/cta-cli | AI (dependencies): Co-versioned sibling package from same TanStack monorepo; not an independent third-party risk. | ai | |
| provenance | no-provenance | AI (provenance): TanStack packages consistently publish without Sigstore provenance; stable false positive for this publisher. | ai | |
| phantom-deps | phantom-dep:@tanstack/create | AI (phantom-deps): Declared runtime dep from same TanStack org; phantom-dep heuristic fires because it's not directly imported in source. | ai |
Versions (showing 7 of 109)
| Version | Deps | Published |
|---|---|---|
| 0.22.2 | 3 / 2 | |
| 0.22.1 | 3 / 2 | |
| 0.22.0 | 3 / 2 | |
| 0.21.0 | 3 / 2 | |
| 0.20.0 | 3 / 2 | |
| 0.19.0 | 3 / 2 | |
| 0.18.0 | 3 / 2 |
v0.22.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.22.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.22.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.21.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.20.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.19.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.18.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.