ast-util Apache 2 21 versions

ast-util

npm Repository Homepage

Utilities for AST transformers.

21

Versions

Apache 2

License

No

Install Scripts

Missing

Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

eventualbuddha

Keywords

asttransformesnextes6macros

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
npm-metadata	url-dep:ast-types	AI (npm-metadata): URL dep points to the publisher's own fork with a named fix branch; same author as the package, early 0.0.1 release. Low supply chain risk for this package.	ai	2026/04/24
license	uncommon-license:Apache 2	AI (license): Apache 2.0 is a well-known permissive license; 'Apache 2' is a non-canonical but unambiguous identifier. No legal concern.	ai	2026/04/24

Versions (showing 21 of 21)

Version	Deps	Published
0.6.0	2 / 2	2014-12-31
0.5.2	2 / 3	2014-10-26
0.5.1	2 / 3	2014-10-15
0.5.0	2 / 3	2014-10-09
0.4.1	2 / 3	2014-09-03
0.4.0	2 / 3	2014-08-26
0.3.4	2 / 3	2014-07-31
0.3.3	2 / 3	2014-07-31
0.3.2	2 / 3	2014-07-31
0.3.1	2 / 3	2014-07-09
0.3.0	2 / 3	2014-06-19
0.2.0	2 / 3	2014-06-13
0.1.2	2 / 3	2014-06-04
0.1.1	2 / 3	2014-05-31
0.1.0	2 / 3	2014-05-31
0.0.6	2 / 3	2014-05-06
0.0.5	2 / 3	2014-04-29
0.0.4	2 / 3	2014-04-29
0.0.3	2 / 3	2014-04-29
0.0.2	2 / 2	2014-04-29
0.0.1	2 / 2	2014-04-27

v0.6.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.5.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.5.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.5.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.4.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.4.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.4

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.6

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.5

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.4

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.