@gearbox-protocol/deploy-tools BUSL-1.1 46 versions

@gearbox-protocol/deploy-tools

npm Repository Homepage

Gearbox deploy tools

46

Versions

BUSL-1.1

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

apeir99ndoomsowermikaellaessserrrelliotyagamivan0kgearbox-devlekhoark57de-snakegregorymel__dabaycode

Keywords

gearbox

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
source-diff	encoded-string-file:dist/index.mjs	AI (source-diff): Long hex strings are EVM bytecode constants bundled from viem; stable false positive for this Ethereum deploy-tools package.	ai	2026/04/30
phantom-deps	phantom-dep:viem-deal	AI (phantom-deps): viem-deal is a declared runtime dep used via config; phantom-dep heuristic fires because it's not directly imported in source.	ai	2026/04/29

Versions (showing 46 of 46)

Version	Deps	Published
6.14.0	1 / 0	2026-06-02
6.13.1	1 / 0	2026-05-20
6.13.0	1 / 0	2026-05-20
6.11.0	1 / 0	2026-05-19
6.10.1	1 / 0	2026-05-18
6.10.0	1 / 0	2026-05-14
6.9.5	1 / 0	2026-05-14
6.9.4	1 / 0	2026-05-12
6.9.3	1 / 0	2026-05-12
6.9.2	1 / 0	2026-05-12
6.9.1	1 / 0	2026-05-09
6.9.0	1 / 0	2026-05-08
6.8.4	1 / 0	2026-05-08
6.8.3	1 / 0	2026-05-08
6.8.2	1 / 0	2026-05-05
6.8.1	1 / 0	2026-05-04
6.8.0	1 / 0	2026-05-04
6.7.1	1 / 0	2026-04-28
6.7.0	0 / 0	2026-04-28
6.6.1	0 / 0	2026-04-28
6.6.0	0 / 0	2026-04-28
6.5.8	0 / 0	2026-04-28
6.5.7	0 / 0	2026-04-27
6.5.6	0 / 0	2026-04-22
6.5.5	0 / 0	2026-04-22
6.5.4	0 / 0	2026-04-22
6.5.3	0 / 0	2026-04-22
6.5.2	0 / 0	2026-04-22
6.5.1	0 / 0	2026-04-22
6.5.0	0 / 0	2026-04-22
6.4.0	0 / 28	2026-04-21
6.3.8	0 / 30	2026-04-20
6.3.7	0 / 30	2026-04-20
6.3.6	0 / 30	2026-04-20
6.3.5	0 / 30	2026-04-20
6.3.4	0 / 30	2026-04-17
6.3.3	0 / 30	2026-04-16
6.3.2	0 / 30	2026-04-16
6.3.1	0 / 30	2026-04-10
6.3.0	0 / 30	2026-04-09
6.2.1	0 / 30	2026-04-09
6.2.0	0 / 30	2026-04-07
6.1.2	0 / 30	2026-04-07
6.1.1	0 / 30	2026-04-01
6.1.0	0 / 30	2026-03-30
6.0.0	0 / 30	2026-03-27

v6.14.0

1 finding

LOW No provenance attestation provenance

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

v6.13.1

1 finding

LOW No provenance attestation provenance

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

v6.13.0

1 finding

LOW No provenance attestation provenance

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

v6.11.0

1 finding

LOW No provenance attestation provenance

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

v6.10.1

1 finding

LOW No provenance attestation provenance

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

v6.10.0

1 finding

LOW No provenance attestation provenance

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

v6.9.5

1 finding

LOW No provenance attestation provenance

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

v6.9.4

1 finding

LOW No provenance attestation provenance

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

v6.9.3

1 finding

LOW No provenance attestation provenance

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

v6.9.2

1 finding

LOW No provenance attestation provenance

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

v6.9.1

1 finding

LOW No provenance attestation provenance

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

v6.9.0

1 finding

LOW No provenance attestation provenance

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

v6.8.4

1 finding

LOW No provenance attestation provenance

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

v6.8.3

1 finding

LOW No provenance attestation provenance

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

v6.8.2

1 finding

LOW No provenance attestation provenance

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

v6.8.1

1 finding

LOW No provenance attestation provenance

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

v6.8.0

1 finding

LOW No provenance attestation provenance

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

v6.7.0

1 finding

LOW No provenance attestation provenance

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

v6.5.8

2 findings

HIGH Long encoded string in modified file: dist/index.mjs source-diff

Modified file contains 16 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.

LOW No provenance attestation provenance

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

v6.5.6

2 findings

HIGH Long encoded string in modified file: dist/index.mjs source-diff

Modified file contains 16 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.

LOW No provenance attestation provenance

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

v6.5.5

2 findings

HIGH Long encoded string in modified file: dist/index.mjs source-diff

Modified file contains 16 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.

LOW No provenance attestation provenance

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

v6.5.1

2 findings

HIGH Long encoded string in modified file: dist/index.mjs source-diff

Modified file contains 16 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.

LOW No provenance attestation provenance

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

v6.5.0

2 findings

HIGH Long encoded string in modified file: dist/index.mjs source-diff

Modified file contains 16 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.

LOW No provenance attestation provenance

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

v6.4.0

2 findings

HIGH Long encoded string in modified file: dist/index.mjs source-diff

Modified file contains 16 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.

LOW No provenance attestation provenance

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

v6.3.7

2 findings

HIGH Long encoded string in modified file: dist/index.mjs source-diff

Modified file contains 16 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.

LOW No provenance attestation provenance

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

v6.3.6

2 findings

HIGH Long encoded string in modified file: dist/index.mjs source-diff

Modified file contains 16 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.

LOW No provenance attestation provenance

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

v6.3.2

2 findings

HIGH Long encoded string in modified file: dist/index.mjs source-diff

Modified file contains 16 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.

LOW No provenance attestation provenance

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

v6.3.0

2 findings

HIGH Long encoded string in modified file: dist/index.mjs source-diff

Modified file contains 16 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.

LOW No provenance attestation provenance

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

v6.1.2

2 findings

HIGH Long encoded string in modified file: dist/index.mjs source-diff

Modified file contains 16 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.

LOW No provenance attestation provenance

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

v6.1.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.

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

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