ts-clone-node
A library that helps you clone Nodes from a Typescript AST
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Established package from known maintainer; lack of provenance attestation is common and not a security concern for this package. | ai | |
| dependencies | unvetted-dep:compatfactory | AI (dependencies): compatfactory is a sibling package by the same author (wessberg), used for TypeScript factory compatibility — a legitimate and expected dependency for this package. | ai |
Versions (showing 20 of 20)
| Version | Deps | Published |
|---|---|---|
| 4.0.0 | 1 / 54 | |
| 3.0.0 | 1 / 53 | |
| 2.0.4 | 1 / 49 | |
| 2.0.3 | 1 / 49 | |
| 2.0.2 | 1 / 49 | |
| 2.0.1 | 1 / 49 | |
| 2.0.0 | 1 / 49 | |
| 1.0.0 | 1 / 46 | |
| 0.3.32 | 1 / 43 | |
| 0.3.30 | 1 / 42 | |
| 0.3.29 | 1 / 42 | |
| 0.3.28 | 1 / 41 | |
| 0.3.27 | 1 / 41 | |
| 0.3.26 | 1 / 41 | |
| 0.3.25 | 1 / 41 | |
| 0.3.24 | 1 / 40 | |
| 0.3.23 | 1 / 40 | |
| 0.3.22 | 1 / 40 | |
| 0.3.21 | 1 / 40 | |
| 0.3.20 | 1 / 39 |
v2.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.32
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.30
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.29
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.28
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.27
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.26
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.23
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.22
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.3.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.