tree-sitter-bash No license 38 versions

tree-sitter-bash

npm Repository Homepage

38

Versions

—

License

Yes

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

ahlincmaxbrunsfeldamaanqnathansobotclemdaviwilqueervioletrewinfreyatom-teamjasonrudolphpatrickthomson

Keywords

incrementalparsingtree-sitterbash

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
phantom-deps	phantom-dep:web-tree-sitter	AI (phantom-deps): WASM binding peer dep, referenced via build-wasm tooling.	ai	2026/07/21
phantom-deps	phantom-dep:prebuild-install	AI (phantom-deps): Known implicit runtime dep for prebuilt binary installs.	ai	2026/07/21
phantom-deps	phantom-dep:nan	AI (phantom-deps): nan is used by native C++ addon build, not JS-imported; standard for node-gyp packages.	ai	2026/07/21
phantom-deps	phantom-dep:node-addon-api	AI (phantom-deps): node-addon-api is used at build time via binding.gyp, not directly imported in JS; stable false positive for native addons.	ai	2026/05/18
install-scripts	install-script:install	AI (install-scripts): node-gyp-build install script is the standard pattern for native addons shipping prebuilts; stable and expected for this package.	ai	2026/04/25
semgrep	semgrep:dynamic-require	AI (semgrep): Dynamic require constructs platform/arch path to load bundled prebuilt binary — fully deterministic and safe, not arbitrary module loading.	ai	2026/04/25
npm-metadata	bundled-binaries	AI (npm-metadata): Prebuilt .node binaries for multiple platforms are the expected output of prebuildify for a tree-sitter grammar binding; not a backdoor risk.	ai	2026/04/25

Versions (showing 38 of 38)

Version	Deps	Published
0.25.1	2 / 4	2025-12-02
0.25.0	2 / 4	2025-06-04
0.21.0	3 / 5	2024-03-13
0.20.5	3 / 5	2024-02-10
0.20.3	3 / 5	2023-08-25
0.20.2	3 / 5	2023-08-23
0.20.1	3 / 5	2023-08-22
0.20.0	3 / 5	2023-08-18
0.19.0	2 / 2	2021-03-04
0.16.1	2 / 2	2020-03-02
0.16.0	2 / 3	2019-07-26
0.15.0	2 / 3	2019-06-19
0.13.9	2 / 3	2019-05-02
0.13.8	2 / 3	2019-04-18
0.13.7	2 / 3	2018-11-06
0.13.6	2 / 3	2018-10-19
0.13.5	2 / 3	2018-10-18
0.13.4	2 / 3	2018-10-18
0.13.3	2 / 3	2018-10-01
0.13.2	2 / 3	2018-08-06
0.13.1	2 / 2	2018-07-23
0.13.0	1 / 1	2018-07-18
0.12.0	1 / 1	2018-06-15
0.11.2	1 / 1	2018-05-24
0.11.1	1 / 1	2018-05-24
0.11.0	1 / 1	2018-03-28
0.6.0	1 / 1	2018-03-06
0.5.5	1 / 1	2018-03-02
0.5.4	1 / 1	2018-03-01
0.5.3	1 / 1	2018-03-01
0.5.2	1 / 1	2018-03-01
0.5.1	1 / 1	2018-03-01
0.5.0	1 / 1	2018-02-13
0.4.2	1 / 1	2017-12-26
0.4.1	1 / 1	2017-12-26
0.4.0	1 / 1	2017-12-22
0.3.0	1 / 1	2017-09-18
0.2.2	1 / 1	2017-08-02

v0.21.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.20.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.20.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.20.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.20.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.20.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.19.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.16.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.16.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.15.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.13.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.13.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.13.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.13.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.13.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.13.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.13.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.13.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.13.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.13.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.12.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.11.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.11.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.11.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.6.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.5.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.5.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.5.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.5.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.5.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.5.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.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.

v0.3.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.2.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.