tsdown
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): Transition to GitHub Actions publisher is backed by SLSA Sigstore attestation from the official rolldown/tsdown repo. | ai | |
| phantom-deps | phantom-dep:lightningcss | AI (phantom-deps): lightningcss is a declared runtime dep used via unplugin-lightningcss; phantom-dep heuristic fires but it's a stable false positive for this package. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): import-without-cache and obug are small, legitimate utilities consistent with a watch-mode refactor (replacing chokidar/diff). No malicious indicators. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): SLSA provenance attestation via Sigstore confirms legitimate CI/CD publish, substantially mitigating account-takeover risk from dormancy. | ai | |
| dependencies | unvetted-dep:rolldown-plugin-dts | AI (dependencies): rolldown-plugin-dts is a core plugin for the rolldown bundler ecosystem that tsdown is built on. | ai | |
| dependencies | unvetted-dep:obug | AI (dependencies): obug is a utility from the same sxzz/rolldown ecosystem; consistent with tsdown's purpose and maintainer. | ai | |
| dependencies | unvetted-dep:import-without-cache | AI (dependencies): import-without-cache is a utility from the same sxzz ecosystem; consistent with tsdown's config loading needs. | ai | |
| dependencies | unvetted-dep:unrun | AI (dependencies): unrun is a utility from the same sxzz/rolldown ecosystem; consistent with tsdown's purpose and maintainer. | ai | |
| dependencies | unvetted-dep:empathic | AI (dependencies): empathic is a path resolution utility from the same ecosystem; consistent with tsdown's bundler use case. | ai | |
| dependencies | unvetted-dep:unconfig-core | AI (dependencies): unconfig-core is a config loading utility from the same ecosystem; consistent with tsdown's bundler use case. | ai |
Versions (showing 51 of 61)
| Version | Deps | Published |
|---|---|---|
| 0.21.10 | 16 / 39 | |
| 0.21.8 | 16 / 39 | |
| 0.21.7 | 16 / 38 | |
| 0.21.6 | 16 / 38 | |
| 0.21.5 | 16 / 38 | |
| 0.18.0 | 15 / 28 | |
| 0.17.1 | 14 / 26 | |
| 0.16.3 | 15 / 22 | |
| 0.16.2 | 15 / 23 | |
| 0.16.1 | 15 / 23 | |
| 0.16.0 | 14 / 24 | |
| 0.15.12 | 14 / 23 | |
| 0.15.11 | 15 / 22 | |
| 0.15.10 | 15 / 22 | |
| 0.15.9 | 14 / 23 | |
| 0.15.8 | 14 / 23 | |
| 0.15.7 | 14 / 23 | |
| 0.15.6 | 14 / 23 | |
| 0.15.5 | 14 / 23 | |
| 0.15.4 | 14 / 22 | |
| 0.15.3 | 14 / 22 | |
| 0.15.2 | 14 / 22 | |
| 0.15.1 | 14 / 22 | |
| 0.15.0 | 14 / 22 | |
| 0.14.2 | 14 / 22 | |
| 0.14.1 | 14 / 30 | |
| 0.14.0 | 14 / 30 | |
| 0.13.5 | 14 / 30 | |
| 0.13.4 | 14 / 30 | |
| 0.13.3 | 14 / 30 | |
| 0.13.2 | 14 / 30 | |
| 0.13.1 | 14 / 30 | |
| 0.13.0 | 13 / 29 | |
| 0.12.9 | 13 / 28 | |
| 0.12.8 | 13 / 28 | |
| 0.12.7 | 13 / 28 | |
| 0.12.6 | 13 / 28 | |
| 0.12.5 | 13 / 27 | |
| 0.12.4 | 13 / 26 | |
| 0.12.3 | 13 / 26 | |
| 0.12.2 | 13 / 26 | |
| 0.12.1 | 13 / 26 | |
| 0.12.0 | 13 / 26 | |
| 0.11.13 | 13 / 26 | |
| 0.11.12 | 13 / 27 | |
| 0.11.11 | 13 / 27 | |
| 0.11.10 | 13 / 27 | |
| 0.11.9 | 13 / 27 | |
| 0.11.8 | 13 / 27 | |
| 0.11.7 | 13 / 27 | |
| 0.11.6 | 13 / 27 |
v0.21.10
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.21.8
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.21.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.21.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.21.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.18.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.17.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.16.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.16.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.16.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.16.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.15.12
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.15.11
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.15.10
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.15.9
2 findingsThis version was published by a different npm account than previous versions on 2025-10-20. 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.
v0.15.8
2 findingsThis version was published by a different npm account than previous versions on 2025-10-18. 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.
v0.15.7
2 findingsThis version was published by a different npm account than previous versions on 2025-10-13. 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.
v0.15.6
2 findingsThis version was published by a different npm account than previous versions on 2025-09-30. 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.
v0.15.5
2 findingsThis version was published by a different npm account than previous versions on 2025-09-27. 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.
v0.15.4
2 findingsThis version was published by a different npm account than previous versions on 2025-09-20. 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.
v0.15.3
2 findingsThis version was published by a different npm account than previous versions on 2025-09-20. 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.
v0.15.2
2 findingsThis version was published by a different npm account than previous versions on 2025-09-16. 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.
v0.15.1
2 findingsThis version was published by a different npm account than previous versions on 2025-09-12. 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.
v0.15.0
2 findingsThis version was published by a different npm account than previous versions on 2025-09-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.
v0.14.2
2 findingsThis version was published by a different npm account than previous versions on 2025-08-25. 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.
v0.14.1
2 findingsThis version was published by a different npm account than previous versions on 2025-08-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.
v0.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.