← Home

burrito

npm Repository

Wrap up expressions with a trace function while walking the AST with rice and beans on the side

19
Versions
BSD
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

substack

Keywords

traceastwalksyntaxsourcetreeuglify

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
source-diff source-size-tripled AI (source-diff): Size increase is entirely explained by addition of Browserify bundles in example/web/. Not an injected payload. ai
source-diff net-exec-file:example/web/bs.js AI (source-diff): Same Browserify vm-shim pattern as browserify.js; located in example/ directory, not runtime code. ai
source-diff obfuscated-file:example/web/bs.js AI (source-diff): example/web/bs.js is a Browserify bundle in the examples directory. Long lines are bundling artifacts, not obfuscation. ai
semgrep semgrep:eval-usage AI (semgrep): eval() is in Script.prototype.runInThisContext — a standard vm module polyfill in Browserify bundles. Not a supply-chain risk in this context. ai
source-diff obfuscated-file:browserify.js AI (source-diff): browserify.js is a standard Browserify bundle (CommonJS module system shim for browsers). Long lines are minified bundle output, not obfuscation. Expected for this package's browser support. ai
source-diff net-exec-file:browserify.js AI (source-diff): The file is a Browserify bundle containing shims for Node core modules (vm, http, etc.). Network and eval patterns are part of the vm module polyfill, not dropper/loader behavior. ai
semgrep semgrep:new-function-constructor AI (semgrep): new Function() usage is in the bundled vm module shim (Script expression compiler). Standard pattern in Browserify bundles for vm compatibility. ai
license uncommon-license:BSD AI (license): BSD is a well-known permissive license; the uncommon-license flag is a false positive for this established open-source package. ai
provenance no-provenance AI (provenance): Package predates Sigstore provenance by many years; absence of attestation is expected and not a risk signal for this package. ai
npm-metadata suspicious-initial-version AI (npm-metadata): This is a 14+ year old established package (uglify-js by Mihai Bazon). The 0.0.0 version label is a routing artifact; the actual package.json version is 1.0.2r1. Not a malware indicator. ai

Versions (showing 19 of 19)

Version Deps Published
0.2.12 2 / 1
0.2.11 2 / 1
0.2.10 2 / 1
0.2.9 2 / 1
0.2.8 2 / 1
0.2.7 2 / 1
0.2.6 2 / 1
0.2.5 2 / 1
0.2.4 2 / 1
0.2.3 2 / 1
0.2.2 2 / 1
0.2.1 2 / 1
0.2.0 2 / 1
0.1.4 2 / 1
0.1.3 2 / 1
0.1.2 2 / 1
0.1.1 1 / 1
0.1.0 1 / 1
0.0.0 0 / 1

v0.2.12

1 finding
LOW No provenance attestation provenance

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

v0.2.11

1 finding
INFO No provenance attestation provenance

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

v0.2.10

3 findings
HIGH New obfuscated file: example/web/bs.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

HIGH New file with network + code execution: example/web/bs.js source-diff

Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.

INFO No provenance attestation provenance

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

v0.2.9

5 findings
HIGH New obfuscated file: browserify.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

HIGH New file with network + code execution: browserify.js source-diff

Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.

HIGH New obfuscated file: example/web/bs.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

HIGH New file with network + code execution: example/web/bs.js source-diff

Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.

INFO No provenance attestation provenance

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

v0.2.8

3 findings
HIGH New obfuscated file: browserify.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

HIGH New file with network + code execution: browserify.js source-diff

Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.

LOW No provenance attestation provenance

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

v0.2.7

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. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.2

1 finding
LOW No provenance attestation provenance

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

v0.2.1

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.4

1 finding
LOW No provenance attestation provenance

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

v0.1.3

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. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.0

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.