← Home

@bitgo/utxo-bin

npm Repository Homepage

Command-line utility for BitGo UTXO transactions

59
Versions
MIT
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

louib-bitgobitgobot

Keywords

bitgoutxobitcoinjsbitcoin

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
dependencies unvetted-dep:clipboardy-cjs AI (dependencies): clipboardy-cjs is a standard CJS wrapper for clipboardy; appropriate for a CLI tool and stable across versions. ai
source-diff obfuscated-file:dist/src/prevTx.js AI (source-diff): Standard tsc output with __createBinding/__importStar helpers, not obfuscation. ai
source-diff obfuscated-file:dist/src/commands/cmdDescriptor/fromFixedScript.js AI (source-diff): Standard TypeScript compiled output; long lines from TS __createBinding boilerplate, not obfuscation. ai
source-diff obfuscated-file:dist/test/cmdDescriptor/fromFixedScript.js AI (source-diff): Standard TypeScript compiled test output; same TS boilerplate pattern, not obfuscation. ai
provenance publisher-changed AI (provenance): bitgobot is BitGo's CI bot with established track record (31 approved packages); consistent with org-wide automation. ai
dependencies unvetted-dep:@bitgo/blockapis AI (dependencies): Internal BitGo monorepo dependency; stable pattern across all @bitgo/* packages. ai
dependencies unvetted-dep:@bitgo/utxo-core AI (dependencies): Internal BitGo monorepo dependency added in this version; stable pattern for this package family. ai
dependencies unvetted-dep:@bitgo/unspents AI (dependencies): Internal BitGo monorepo dependency; stable pattern across all @bitgo/* packages. ai

Versions (showing 59 of 59)

Version Deps Published
3.25.3 16 / 3
3.25.2 16 / 3
3.25.1 16 / 3
3.25.0 16 / 3
3.24.1 16 / 3
3.24.0 16 / 3
3.23.1 16 / 3
3.23.0 16 / 3
3.22.3 16 / 3
3.22.2 16 / 3
3.22.1 16 / 3
3.22.0 16 / 3
3.21.3 16 / 3
3.21.2 16 / 3
3.21.1 16 / 3
3.21.0 16 / 3
3.20.4 16 / 3
3.20.3 16 / 3
3.20.2 16 / 3
3.20.1 16 / 3
3.20.0 16 / 3
3.19.0 16 / 3
3.18.0 16 / 3
3.17.1 16 / 3
3.16.0 16 / 3
3.15.0 16 / 3
3.14.0 16 / 3
3.13.3 16 / 3
3.13.2 16 / 3
3.13.1 16 / 3
3.13.0 16 / 3
3.12.2 16 / 3
3.12.1 16 / 3
3.12.0 16 / 3
3.11.0 16 / 3
3.10.11 16 / 3
3.10.8 16 / 3
3.10.4 16 / 3
3.10.3 16 / 3
3.9.3 16 / 3
3.9.2 16 / 3
3.9.1 16 / 3
3.9.0 16 / 3
3.8.9 16 / 3
3.8.8 16 / 3
3.8.7 16 / 3
3.8.6 16 / 3
3.8.5 16 / 3
3.8.4 16 / 3
3.8.3 16 / 3
3.8.2 16 / 3
3.8.1 16 / 3
3.8.0 16 / 3
3.7.3 15 / 3
3.7.2 15 / 3
3.7.1 15 / 3
3.7.0 15 / 3
3.6.19 15 / 3
3.6.13 15 / 3

v3.25.3

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v3.25.2

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v3.25.1

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v3.25.0

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v3.24.1

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v3.24.0

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v3.23.1

6 findings
HIGH Complete maintainer takeover detected maintainer-change

All previous maintainers (pengyuc_bitgo, dhoffmann, bitgoaaron, mmcshinsky-bitgo, ericcrosson-bitgo, johntzanakakisbitgo, joshdk, margueriteblair, pranavjain, islamaminbitgo, mkottaichamy, zahin-mohammad, mohammadalfaiyaz_bitgo) were replaced by new maintainers (louib-bitgo, bitgobot). This is a strong signal of a potential package hijack and requires careful review.

HIGH Publisher changed: mohammadalfaiyaz_bitgo → GitHub Actions (on 2026-05-05) provenance

This version was published by a different npm account than previous versions on 2026-05-05. This could indicate a legitimate maintainer transition or an account compromise.

HIGH New obfuscated file: dist/src/commands/cmdDescriptor/fromFixedScript.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 obfuscated file: dist/test/cmdDescriptor/fromFixedScript.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 obfuscated file: dist/src/prevTx.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.

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v3.23.0

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v3.22.3

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v3.22.2

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v3.22.1

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v3.22.0

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v3.21.3

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v3.21.2

2 findings
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

INFO Publisher changed: bitgobot → GitHub Actions (on 2026-03-29) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2026-03-29. This could indicate a legitimate maintainer transition or an account compromise.

v3.21.1

2 findings
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

INFO Publisher changed: bitgobot → GitHub Actions (on 2026-03-27) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2026-03-27. This could indicate a legitimate maintainer transition or an account compromise.

v3.21.0

2 findings
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

INFO Publisher changed: bitgobot → GitHub Actions (on 2026-03-18) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2026-03-18. This could indicate a legitimate maintainer transition or an account compromise.

v3.20.4

2 findings
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

INFO Publisher changed: bitgobot → GitHub Actions (on 2026-03-10) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2026-03-10. This could indicate a legitimate maintainer transition or an account compromise.

v3.20.3

1 finding
LOW No provenance attestation provenance

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

v3.20.2

1 finding
LOW No provenance attestation provenance

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

v3.20.1

1 finding
LOW No provenance attestation provenance

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

v3.20.0

1 finding
LOW No provenance attestation provenance

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

v3.19.0

1 finding
LOW No provenance attestation provenance

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

v3.18.0

1 finding
LOW No provenance attestation provenance

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

v3.17.1

1 finding
LOW No provenance attestation provenance

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

v3.16.0

1 finding
LOW No provenance attestation provenance

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

v3.15.0

1 finding
LOW No provenance attestation provenance

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

v3.14.0

1 finding
LOW No provenance attestation provenance

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

v3.13.3

1 finding
LOW No provenance attestation provenance

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

v3.13.2

1 finding
LOW No provenance attestation provenance

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

v3.13.1

1 finding
LOW No provenance attestation provenance

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

v3.13.0

1 finding
LOW No provenance attestation provenance

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

v3.12.2

1 finding
LOW No provenance attestation provenance

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

v3.12.1

1 finding
LOW No provenance attestation provenance

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

v3.12.0

1 finding
LOW No provenance attestation provenance

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

v3.11.0

1 finding
LOW No provenance attestation provenance

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

v3.10.11

1 finding
LOW No provenance attestation provenance

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

v3.10.8

4 findings
HIGH Publisher changed: mohammadalfaiyaz_bitgo → bitgobot (on 2025-10-24) provenance

This version was published by a different npm account than previous versions on 2025-10-24. This could indicate a legitimate maintainer transition or an account compromise.

HIGH New obfuscated file: dist/src/commands/cmdDescriptor/fromFixedScript.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 obfuscated file: dist/test/cmdDescriptor/fromFixedScript.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.

LOW No provenance attestation provenance

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

v3.10.4

4 findings
HIGH Publisher changed: mohammadalfaiyaz_bitgo → bitgobot (on 2025-10-09) provenance

This version was published by a different npm account than previous versions on 2025-10-09. This could indicate a legitimate maintainer transition or an account compromise.

HIGH New obfuscated file: dist/src/commands/cmdDescriptor/fromFixedScript.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 obfuscated file: dist/test/cmdDescriptor/fromFixedScript.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.

LOW No provenance attestation provenance

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

v3.10.3

4 findings
HIGH Publisher changed: mohammadalfaiyaz_bitgo → bitgobot (on 2025-10-08) provenance

This version was published by a different npm account than previous versions on 2025-10-08. This could indicate a legitimate maintainer transition or an account compromise.

HIGH New obfuscated file: dist/src/commands/cmdDescriptor/fromFixedScript.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 obfuscated file: dist/test/cmdDescriptor/fromFixedScript.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.

LOW No provenance attestation provenance

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

v3.9.3

4 findings
HIGH Publisher changed: mohammadalfaiyaz_bitgo → pranavjain (on 2025-09-03) provenance

This version was published by a different npm account than previous versions on 2025-09-03. This could indicate a legitimate maintainer transition or an account compromise.

HIGH New obfuscated file: dist/src/commands/cmdDescriptor/fromFixedScript.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 obfuscated file: dist/test/cmdDescriptor/fromFixedScript.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.

LOW No provenance attestation provenance

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

v3.9.2

4 findings
HIGH Publisher changed: mohammadalfaiyaz_bitgo → zahin-mohammad (on 2025-08-29) provenance

This version was published by a different npm account than previous versions on 2025-08-29. This could indicate a legitimate maintainer transition or an account compromise.

HIGH New obfuscated file: dist/src/commands/cmdDescriptor/fromFixedScript.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 obfuscated file: dist/test/cmdDescriptor/fromFixedScript.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.

LOW No provenance attestation provenance

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

v3.9.1

4 findings
HIGH Publisher changed: mohammadalfaiyaz_bitgo → pranavjain (on 2025-08-27) provenance

This version was published by a different npm account than previous versions on 2025-08-27. This could indicate a legitimate maintainer transition or an account compromise.

HIGH New obfuscated file: dist/src/commands/cmdDescriptor/fromFixedScript.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 obfuscated file: dist/test/cmdDescriptor/fromFixedScript.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.

LOW No provenance attestation provenance

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

v3.9.0

4 findings
HIGH Publisher changed: mohammadalfaiyaz_bitgo → zahin-mohammad (on 2025-08-22) provenance

This version was published by a different npm account than previous versions on 2025-08-22. This could indicate a legitimate maintainer transition or an account compromise.

HIGH New obfuscated file: dist/src/commands/cmdDescriptor/fromFixedScript.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 obfuscated file: dist/test/cmdDescriptor/fromFixedScript.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.

LOW No provenance attestation provenance

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

v3.8.9

4 findings
HIGH Publisher changed: mohammadalfaiyaz_bitgo → zahin-mohammad (on 2025-08-22) provenance

This version was published by a different npm account than previous versions on 2025-08-22. This could indicate a legitimate maintainer transition or an account compromise.

HIGH New obfuscated file: dist/src/commands/cmdDescriptor/fromFixedScript.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 obfuscated file: dist/test/cmdDescriptor/fromFixedScript.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.

LOW No provenance attestation provenance

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

v3.8.8

4 findings
HIGH Publisher changed: mohammadalfaiyaz_bitgo → zahin-mohammad (on 2025-08-19) provenance

This version was published by a different npm account than previous versions on 2025-08-19. This could indicate a legitimate maintainer transition or an account compromise.

HIGH New obfuscated file: dist/src/commands/cmdDescriptor/fromFixedScript.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 obfuscated file: dist/test/cmdDescriptor/fromFixedScript.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.

LOW No provenance attestation provenance

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

v3.8.7

4 findings
HIGH Publisher changed: mohammadalfaiyaz_bitgo → zahin-mohammad (on 2025-08-14) provenance

This version was published by a different npm account than previous versions on 2025-08-14. This could indicate a legitimate maintainer transition or an account compromise.

HIGH New obfuscated file: dist/src/commands/cmdDescriptor/fromFixedScript.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 obfuscated file: dist/test/cmdDescriptor/fromFixedScript.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.

LOW No provenance attestation provenance

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

v3.8.6

3 findings
HIGH New obfuscated file: dist/src/commands/cmdDescriptor/fromFixedScript.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 obfuscated file: dist/test/cmdDescriptor/fromFixedScript.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.

LOW No provenance attestation provenance

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

v3.8.5

3 findings
HIGH New obfuscated file: dist/src/commands/cmdDescriptor/fromFixedScript.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 obfuscated file: dist/test/cmdDescriptor/fromFixedScript.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.

LOW No provenance attestation provenance

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

v3.8.4

3 findings
HIGH New obfuscated file: dist/src/commands/cmdDescriptor/fromFixedScript.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 obfuscated file: dist/test/cmdDescriptor/fromFixedScript.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.

LOW No provenance attestation provenance

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

v3.8.3

3 findings
HIGH New obfuscated file: dist/src/commands/cmdDescriptor/fromFixedScript.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 obfuscated file: dist/test/cmdDescriptor/fromFixedScript.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.

LOW No provenance attestation provenance

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

v3.8.2

3 findings
HIGH New obfuscated file: dist/src/commands/cmdDescriptor/fromFixedScript.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 obfuscated file: dist/test/cmdDescriptor/fromFixedScript.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.

LOW No provenance attestation provenance

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

v3.8.1

4 findings
HIGH Publisher changed: mohammadalfaiyaz_bitgo → pranavjain (on 2025-07-15) provenance

This version was published by a different npm account than previous versions on 2025-07-15. This could indicate a legitimate maintainer transition or an account compromise.

HIGH New obfuscated file: dist/src/commands/cmdDescriptor/fromFixedScript.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 obfuscated file: dist/test/cmdDescriptor/fromFixedScript.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.

LOW No provenance attestation provenance

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

v3.8.0

4 findings
HIGH Publisher changed: mohammadalfaiyaz_bitgo → zahin-mohammad (on 2025-07-10) provenance

This version was published by a different npm account than previous versions on 2025-07-10. This could indicate a legitimate maintainer transition or an account compromise.

HIGH New obfuscated file: dist/src/commands/cmdDescriptor/fromFixedScript.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 obfuscated file: dist/test/cmdDescriptor/fromFixedScript.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.

LOW No provenance attestation provenance

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

v3.7.3

2 findings
HIGH Publisher changed: mohammadalfaiyaz_bitgo → zahin-mohammad (on 2025-07-03) provenance

This version was published by a different npm account than previous versions on 2025-07-03. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

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

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

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

v3.6.19

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.

v3.6.13

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.