← Home

@kerebron/wasm

npm
39
Versions
—
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, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

ggodlewskihorner

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
semgrep semgrep:api-obfuscation-reflect AI (semgrep): Standard dnt polyfill boilerplate, not evasive obfuscation. ai
bogus-package bogus-package AI (bogus-package): Small utility mirror package; no malicious behavior indicated. ai
npm-metadata bundled-binaries AI (npm-metadata): Package's stated purpose is mirroring tree-sitter grammar wasm files. ai
source-diff obfuscated-file:assets/tree-sitter/web-tree-sitter.js AI (source-diff): Bundled upstream tree-sitter loader, minified not obfuscated. ai
semgrep semgrep:eval-usage AI (semgrep): Emscripten ASM_CONSTS eval pattern in upstream bundle. ai
semgrep semgrep:toplevel-fetch AI (semgrep): Fetches the module's own wasm binary, not exfiltration. ai
source-diff net-exec-file:assets/tree-sitter/web-tree-sitter.js AI (source-diff): fetch loads companion .wasm binary; eval is emscripten ASM_CONSTS, standard pattern. ai

Versions (showing 39 of 39)

Version Deps Published
0.8.6 1 / 1
0.8.4 1 / 1
0.8.3 1 / 1
0.8.2 1 / 1
0.8.1 1 / 1
0.7.9 1 / 1
0.7.8 1 / 1
0.7.7 1 / 1
0.7.6 1 / 1
0.7.5 1 / 1
0.7.4 1 / 1
0.7.3 1 / 1
0.7.2 1 / 1
0.7.1 1 / 1
0.7.0 1 / 1
0.6.7 1 / 1
0.6.6 1 / 1
0.6.5 1 / 1
0.6.4 1 / 1
0.6.3 1 / 1
0.6.2 1 / 1
0.6.1 1 / 1
0.6.0 1 / 1
0.5.5 0 / 1
0.5.4 0 / 1
0.5.0 0 / 1
0.4.12 0 / 1
0.4.11 0 / 1
0.4.10 0 / 1
0.4.9 0 / 1
0.4.8 0 / 1
0.4.7 0 / 1
0.4.6 0 / 1
0.4.5 0 / 1
0.4.4 0 / 1
0.4.3 0 / 1
0.4.2 1 / 1
0.4.1 1 / 1
0.4.0 1 / 1

v0.8.6

2 findings
HIGH Bundled binary files (20) npm-metadata

Package contains compiled binaries that could be backdoors: • assets/odt-wasm/odt-parser-debug.wasm • assets/odt-wasm/odt-parser.wasm • assets/tree-sitter-css/tree-sitter-css.wasm • assets/tree-sitter-diff/tree-sitter-diff.wasm • assets/tree-sitter-xml/tree-sitter-dtd.wasm • assets/tree-sitter-html/tree-sitter-html.wasm • assets/tree-sitter-java/tree-sitter-java.wasm • assets/tree-sitter-javascript/tree-sitter-javascript.wasm • assets/tree-sitter-json/tree-sitter-json.wasm • assets/tree-sitter-markdown/tree-sitter-markdown_inline.wasm ... and 10 more

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

4 findings
HIGH Bundled binary files (20) npm-metadata

Package contains compiled binaries that could be backdoors: • assets/odt-wasm/odt-parser-debug.wasm • assets/odt-wasm/odt-parser.wasm • assets/tree-sitter-css/tree-sitter-css.wasm • assets/tree-sitter-diff/tree-sitter-diff.wasm • assets/tree-sitter-xml/tree-sitter-dtd.wasm • assets/tree-sitter-html/tree-sitter-html.wasm • assets/tree-sitter-java/tree-sitter-java.wasm • assets/tree-sitter-javascript/tree-sitter-javascript.wasm • assets/tree-sitter-json/tree-sitter-json.wasm • assets/tree-sitter-markdown/tree-sitter-markdown_inline.wasm ... and 10 more

HIGH New obfuscated file: assets/tree-sitter/web-tree-sitter.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: assets/tree-sitter/web-tree-sitter.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.8.3

4 findings
HIGH Bundled binary files (20) npm-metadata

Package contains compiled binaries that could be backdoors: • assets/odt-wasm/odt-parser-debug.wasm • assets/odt-wasm/odt-parser.wasm • assets/tree-sitter-css/tree-sitter-css.wasm • assets/tree-sitter-diff/tree-sitter-diff.wasm • assets/tree-sitter-xml/tree-sitter-dtd.wasm • assets/tree-sitter-html/tree-sitter-html.wasm • assets/tree-sitter-java/tree-sitter-java.wasm • assets/tree-sitter-javascript/tree-sitter-javascript.wasm • assets/tree-sitter-json/tree-sitter-json.wasm • assets/tree-sitter-markdown/tree-sitter-markdown_inline.wasm ... and 10 more

HIGH New obfuscated file: assets/tree-sitter/web-tree-sitter.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: assets/tree-sitter/web-tree-sitter.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.8.2

4 findings
HIGH Bundled binary files (20) npm-metadata

Package contains compiled binaries that could be backdoors: • assets/odt-wasm/odt-parser-debug.wasm • assets/odt-wasm/odt-parser.wasm • assets/tree-sitter-css/tree-sitter-css.wasm • assets/tree-sitter-diff/tree-sitter-diff.wasm • assets/tree-sitter-xml/tree-sitter-dtd.wasm • assets/tree-sitter-html/tree-sitter-html.wasm • assets/tree-sitter-java/tree-sitter-java.wasm • assets/tree-sitter-javascript/tree-sitter-javascript.wasm • assets/tree-sitter-json/tree-sitter-json.wasm • assets/tree-sitter-markdown/tree-sitter-markdown_inline.wasm ... and 10 more

HIGH New obfuscated file: assets/tree-sitter/web-tree-sitter.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: assets/tree-sitter/web-tree-sitter.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.8.1

4 findings
HIGH Bundled binary files (20) npm-metadata

Package contains compiled binaries that could be backdoors: • assets/odt-wasm/odt-parser-debug.wasm • assets/odt-wasm/odt-parser.wasm • assets/tree-sitter-css/tree-sitter-css.wasm • assets/tree-sitter-diff/tree-sitter-diff.wasm • assets/tree-sitter-xml/tree-sitter-dtd.wasm • assets/tree-sitter-html/tree-sitter-html.wasm • assets/tree-sitter-java/tree-sitter-java.wasm • assets/tree-sitter-javascript/tree-sitter-javascript.wasm • assets/tree-sitter-json/tree-sitter-json.wasm • assets/tree-sitter-markdown/tree-sitter-markdown_inline.wasm ... and 10 more

HIGH New obfuscated file: assets/tree-sitter/web-tree-sitter.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: assets/tree-sitter/web-tree-sitter.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.7.9

1 finding
LOW No provenance attestation provenance

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

v0.7.8

1 finding
LOW No provenance attestation provenance

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

v0.7.7

1 finding
LOW No provenance attestation provenance

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

v0.7.6

1 finding
LOW No provenance attestation provenance

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

v0.7.5

1 finding
LOW No provenance attestation provenance

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

v0.7.4

1 finding
LOW No provenance attestation provenance

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

v0.7.3

1 finding
LOW No provenance attestation provenance

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

v0.7.2

1 finding
LOW No provenance attestation provenance

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

v0.7.1

1 finding
LOW No provenance attestation provenance

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

v0.7.0

1 finding
LOW No provenance attestation provenance

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

v0.6.7

1 finding
LOW No provenance attestation provenance

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

v0.6.6

1 finding
LOW No provenance attestation provenance

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

v0.6.5

1 finding
LOW No provenance attestation provenance

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

v0.6.4

1 finding
LOW No provenance attestation provenance

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

v0.6.3

1 finding
LOW No provenance attestation provenance

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

v0.6.2

1 finding
LOW No provenance attestation provenance

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

v0.6.1

1 finding
LOW No provenance attestation provenance

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

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

1 finding
LOW No provenance attestation provenance

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

v0.5.4

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

1 finding
LOW No provenance attestation provenance

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

v0.4.11

1 finding
LOW No provenance attestation provenance

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

v0.4.10

1 finding
LOW No provenance attestation provenance

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

v0.4.9

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

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

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

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

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

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

v0.4.2

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

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