← Home

fresh-falafel

npm Repository Homepage

transform the ast on a recursive walk

5
Versions
MIT
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

royriojas

Keywords

astburritosourcesyntaxtraversaltree

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
npm-metadata url-dep:esprima AI (npm-metadata): Historical git-fork dependency on substack/esprima#is-keyword is a known stable pattern from early npm ecosystem; package is 11+ years old and this dep has been unchanged throughout its lifetime. ai
provenance no-provenance AI (provenance): Package predates Sigstore provenance on npm by many years; absence is expected and not a risk signal for this package. ai

Versions (showing 5 of 5)

Version Deps Published
1.2.0 4 / 3
0.2.6 1 / 2
0.2.5 1 / 2
0.2.4 1 / 2
0.2.3 1 / 2

v1.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.2.6

1 finding
LOW No provenance attestation provenance

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

v0.2.5

1 finding
LOW No provenance attestation provenance

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

v0.2.4

1 finding
LOW No provenance attestation provenance

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

v0.2.3

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.