@zokugun/tsc-leda
CLI utility compiling (with `tsc`) and preparing TS projects for dual ESM/CJS distribution
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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Publisher is GitHub Actions CI/CD with SLSA provenance attestation; this is the expected publish pattern for this package going forward. | ai | |
| install-scripts | install-script:postinstall | AI (install-scripts): postinstall runs patch-package, a declared runtime dep; standard patching pattern, not arbitrary code execution. | ai | |
| phantom-deps | phantom-dep:patch-package | AI (phantom-deps): patch-package is invoked via postinstall script, not imported directly; phantom-dep false positive for this package. | ai | |
| phantom-deps | phantom-dep:enquirer | AI (phantom-deps): enquirer is a CLI prompt library likely used at runtime via dynamic invocation; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@zokugun/log-update-plus | AI (phantom-deps): Same-org scoped dep; likely used transitively or indirectly — stable false positive for this package. | ai | |
| provenance | slsa-provenance | AI (provenance): Published via CI/CD with Sigstore SLSA attestation; stable supply chain signal for this package. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 0.4.2 | 8 / 16 | |
| 0.4.1 | 8 / 16 | |
| 0.4.0 | 8 / 15 | |
| 0.3.2 | 8 / 16 | |
| 0.3.1 | 12 / 15 | |
| 0.3.0 | 12 / 15 | |
| 0.2.0 | 12 / 12 | |
| 0.1.3 | 12 / 13 | |
| 0.1.1 | 12 / 13 | |
| 0.1.0 | 12 / 13 |
v0.4.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.4.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.4.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.3.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.3.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.3.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.2.0
2 findingsScript: patch-package
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.1.3
2 findingsThis version was published by a different npm account than previous versions on 2026-01-15. 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.1.1
2 findingsThis version was published by a different npm account than previous versions on 2026-01-14. 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.1.0
2 findingsScript: patch-package
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.