← Home

@bitgo/sdk-coin-atom

npm Repository Homepage

BitGo SDK coin library for Cosmos

43
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

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
maintainer-change maintainer-takeover AI (maintainer-change): bitgobot is BitGo's automation account with 498 approved packages; consistent with org-wide pipeline migration. ai
source-diff obfuscated-file:dist/test/unit/transactionBuilder/transactionBuilder.js AI (source-diff): Compiled TypeScript unit test; standard tsc output pattern. ai
source-diff obfuscated-file:dist/test/unit/transactionBuilder/transferBuilder.js AI (source-diff): Compiled TypeScript unit test; standard tsc output pattern. ai
source-diff obfuscated-file:dist/test/unit/utils.js AI (source-diff): Compiled TypeScript unit test; standard tsc output pattern. ai
source-diff obfuscated-file:dist/test/resources/atom.js AI (source-diff): Compiled TypeScript test fixture; long lines are base64 test vectors, not obfuscation. ai
source-diff obfuscated-file:dist/test/unit/atom.js AI (source-diff): Standard tsc-compiled unit test output; readable test logic visible in sample. ai
source-diff obfuscated-file:dist/test/unit/keyPair.js AI (source-diff): Compiled TypeScript unit test; long lines from test data, not obfuscation. ai
source-diff obfuscated-file:dist/test/unit/transactionBuilder/StakingActivateBuilder.js AI (source-diff): Compiled TypeScript unit test; standard tsc output pattern. ai
source-diff obfuscated-file:dist/test/unit/transactionBuilder/StakingDeactivateBuilder.js AI (source-diff): Compiled TypeScript unit test; standard tsc output pattern. ai
source-diff obfuscated-file:dist/test/unit/transactionBuilder/StakingRedelegateBuilder.js AI (source-diff): Compiled TypeScript unit test; standard tsc output pattern. ai
source-diff obfuscated-file:dist/test/unit/transactionBuilder/StakingWithdrawRewardsBuilder.js AI (source-diff): Compiled TypeScript unit test; standard tsc output pattern. ai
source-diff obfuscated-file:dist/test/unit/transaction.js AI (source-diff): Compiled TypeScript unit test; standard tsc output pattern. ai
provenance publisher-changed AI (provenance): zahin-mohammad is an established BitGo org publisher with 321 approvals; transition appears legitimate. ai
phantom-deps phantom-dep:@bitgo/sdk-lib-mpc AI (phantom-deps): Same-org transitive usage; stable false positive for this BitGo monorepo package. ai
phantom-deps phantom-dep:@cosmjs/encoding AI (phantom-deps): Declared as runtime dep; phantom-dep heuristic false positive for this package. ai

Versions (showing 43 of 43)

Version Deps Published
13.13.2 8 / 4
13.13.1 8 / 4
13.13.0 8 / 4
13.12.11 8 / 4
13.12.10 8 / 4
13.12.9 8 / 4
13.12.8 8 / 4
13.12.7 8 / 4
13.12.6 8 / 4
13.11.0 8 / 4
13.9.9 8 / 4
13.9.5 8 / 4
13.9.3 8 / 4
13.9.2 8 / 4
13.9.1 8 / 4
13.9.0 8 / 4
13.8.2 8 / 4
13.8.1 8 / 4
13.8.0 8 / 4
13.7.1 8 / 4
13.7.0 8 / 4
13.6.3 8 / 4
13.6.2 8 / 4
13.6.1 8 / 4
13.6.0 8 / 4
13.5.11 8 / 4
13.5.10 8 / 4
13.5.9 8 / 4
13.5.8 8 / 4
13.5.7 8 / 4
13.5.6 8 / 4
13.5.5 8 / 4
13.5.4 8 / 4
13.5.3 8 / 4
13.5.2 8 / 4
13.5.1 8 / 4
13.5.0 8 / 4
13.4.14 8 / 4
13.4.13 8 / 4
13.4.12 8 / 4
13.4.11 8 / 4
13.4.10 8 / 4
13.4.9 8 / 4

v13.13.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.

v13.13.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.

v13.13.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.

v13.12.11

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.

v13.12.10

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.

v13.12.9

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.

v13.12.8

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.

v13.12.7

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.

v13.12.6

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.

v13.11.0

14 findings
HIGH Complete maintainer takeover detected maintainer-change

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

HIGH Publisher changed: mohammadalfaiyaz_bitgo → bitgobot (on 2026-02-12) provenance

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

HIGH New obfuscated file: dist/test/resources/atom.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/unit/atom.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/unit/keyPair.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/unit/transactionBuilder/StakingActivateBuilder.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/unit/transactionBuilder/StakingDeactivateBuilder.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/unit/transactionBuilder/StakingRedelegateBuilder.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/unit/transactionBuilder/StakingWithdrawRewardsBuilder.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/unit/transaction.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/unit/transactionBuilder/transactionBuilder.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/unit/transactionBuilder/transferBuilder.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/unit/utils.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.

v13.9.9

14 findings
HIGH Complete maintainer takeover detected maintainer-change

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

HIGH Publisher changed: mohammadalfaiyaz_bitgo → bitgobot (on 2025-10-29) provenance

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

HIGH New obfuscated file: dist/test/resources/atom.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/unit/atom.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/unit/keyPair.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/unit/transactionBuilder/StakingActivateBuilder.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/unit/transactionBuilder/StakingDeactivateBuilder.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/unit/transactionBuilder/StakingRedelegateBuilder.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/unit/transactionBuilder/StakingWithdrawRewardsBuilder.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/unit/transaction.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/unit/transactionBuilder/transactionBuilder.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/unit/transactionBuilder/transferBuilder.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/unit/utils.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.

v13.9.5

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

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

HIGH New obfuscated file: dist/test/resources/atom.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/unit/atom.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/unit/keyPair.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/unit/transactionBuilder/StakingActivateBuilder.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/unit/transactionBuilder/StakingDeactivateBuilder.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/unit/transactionBuilder/StakingRedelegateBuilder.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/unit/transactionBuilder/StakingWithdrawRewardsBuilder.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/unit/transaction.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/unit/transactionBuilder/transactionBuilder.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/unit/transactionBuilder/transferBuilder.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/unit/utils.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.

v13.9.3

13 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/test/resources/atom.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/unit/atom.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/unit/keyPair.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/unit/transactionBuilder/StakingActivateBuilder.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/unit/transactionBuilder/StakingDeactivateBuilder.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/unit/transactionBuilder/StakingRedelegateBuilder.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/unit/transactionBuilder/StakingWithdrawRewardsBuilder.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/unit/transaction.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/unit/transactionBuilder/transactionBuilder.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/unit/transactionBuilder/transferBuilder.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/unit/utils.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.

v13.9.2

2 findings
HIGH Publisher changed: mohammadalfaiyaz_bitgo → bitgobot (on 2025-10-02) provenance

This version was published by a different npm account than previous versions on 2025-10-02. 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.

v13.9.1

2 findings
HIGH Publisher changed: mohammadalfaiyaz_bitgo → bitgobot (on 2025-09-29) provenance

This version was published by a different npm account than previous versions on 2025-09-29. 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.

v13.9.0

2 findings
HIGH Publisher changed: mohammadalfaiyaz_bitgo → bitgobot (on 2025-09-25) provenance

This version was published by a different npm account than previous versions on 2025-09-25. 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.

v13.8.2

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

LOW No provenance attestation provenance

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

v13.8.1

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

This version was published by a different npm account than previous versions on 2025-08-30. 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.

v13.8.0

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

LOW No provenance attestation provenance

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

v13.7.1

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

LOW No provenance attestation provenance

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

v13.7.0

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

LOW No provenance attestation provenance

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

v13.6.3

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

LOW No provenance attestation provenance

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

v13.6.2

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

LOW No provenance attestation provenance

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

v13.6.1

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

LOW No provenance attestation provenance

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

v13.6.0

1 finding
LOW No provenance attestation provenance

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

v13.5.11

1 finding
LOW No provenance attestation provenance

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

v13.5.10

1 finding
LOW No provenance attestation provenance

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

v13.5.9

1 finding
LOW No provenance attestation provenance

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

v13.5.8

1 finding
LOW No provenance attestation provenance

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

v13.5.7

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

LOW No provenance attestation provenance

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

v13.5.6

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

LOW No provenance attestation provenance

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

v13.5.5

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.

v13.5.4

1 finding
LOW No provenance attestation provenance

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

v13.5.3

1 finding
LOW No provenance attestation provenance

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

v13.5.2

1 finding
LOW No provenance attestation provenance

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

v13.5.1

1 finding
LOW No provenance attestation provenance

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

v13.5.0

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

This version was published by a different npm account than previous versions on 2025-06-05. 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.

v13.4.14

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

This version was published by a different npm account than previous versions on 2025-06-02. 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.

v13.4.13

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

This version was published by a different npm account than previous versions on 2025-05-28. 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.

v13.4.12

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.

v13.4.11

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.

v13.4.10

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.

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