← Home

@bitgo/abstract-cosmos

npm Repository Homepage

BitGo SDK coin library for COSMOS base implementation

51
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
phantom-deps phantom-dep:@cosmjs/proto-signing AI (phantom-deps): Declared and used indirectly; stable pattern for SDK re-exports. ai
phantom-deps phantom-dep:@bitgo/statics AI (phantom-deps): Same-org scoped dep; used indirectly in SDK architecture. ai
phantom-deps phantom-dep:@cosmjs/crypto AI (phantom-deps): Declared and used indirectly; stable pattern for SDK re-exports. ai
phantom-deps phantom-dep:@bitgo/sdk-core AI (phantom-deps): Same-org scoped dep; used indirectly in SDK architecture. ai
phantom-deps phantom-dep:@bitgo/secp256k1 AI (phantom-deps): Same-org scoped dep; used indirectly in SDK architecture. ai
phantom-deps phantom-dep:@cosmjs/encoding AI (phantom-deps): Declared and used indirectly; stable pattern for SDK re-exports. ai
phantom-deps phantom-dep:@cosmjs/stargate AI (phantom-deps): Declared and used indirectly; stable pattern for SDK re-exports. ai
phantom-deps phantom-dep:@bitgo/sdk-lib-mpc AI (phantom-deps): Same-org scoped dep; used indirectly in SDK architecture. ai
phantom-deps phantom-dep:lodash AI (phantom-deps): Declared and used indirectly; stable pattern for SDK re-exports. ai
phantom-deps phantom-dep:superagent AI (phantom-deps): Declared and used indirectly; stable pattern for SDK re-exports. ai
phantom-deps phantom-dep:bignumber.js AI (phantom-deps): Declared and used indirectly; stable pattern for SDK re-exports. ai
phantom-deps phantom-dep:cosmjs-types AI (phantom-deps): Declared and used indirectly; stable pattern for SDK re-exports. ai
phantom-deps phantom-dep:@cosmjs/amino AI (phantom-deps): Declared and used indirectly; stable pattern for SDK re-exports. ai
source-diff obfuscated-file:dist/src/cosmosToken.js AI (source-diff): Sample shows standard TS-compiled JS; long lines are from token iteration, not obfuscation. ai
maintainer-change maintainer-takeover AI (maintainer-change): BitGo consolidated all packages under bitgobot automation account; 794 approved packages confirm legitimate org-wide transition. ai
maintainer-change maintainer-removed AI (maintainer-change): Removal of individual maintainers is part of BitGo's org-wide consolidation to bitgobot. ai
provenance no-provenance AI (provenance): BitGo does not use Sigstore provenance; stable pattern across all their packages. ai
maintainer-change maintainer-added AI (maintainer-change): louib-bitgo is a BitGo org member; addition consistent with normal team management for this established package. ai
provenance publisher-changed AI (provenance): BitGo migrated publishing to GitHub Actions CI with SLSA attestation; stable pattern for this org's packages. ai
bogus-package bogus-package AI (bogus-package): Established BitGo SDK module; sparse README/no keywords is a style choice, not a spam indicator. ai

Versions (showing 51 of 76)

View all versions
Version Deps Published
11.19.2 14 / 1
11.19.1 14 / 1
11.19.0 14 / 1
11.18.11 14 / 1
11.18.10 14 / 1
11.18.9 14 / 1
11.18.8 14 / 1
11.18.7 14 / 1
11.18.6 14 / 1
11.18.5 14 / 1
11.18.4 14 / 1
11.18.3 14 / 1
11.18.2 14 / 1
11.18.1 14 / 1
11.18.0 14 / 1
11.17.8 14 / 1
11.17.7 14 / 1
11.17.6 14 / 1
11.17.5 14 / 1
11.17.4 14 / 1
11.17.3 14 / 1
11.17.2 14 / 1
11.17.1 14 / 1
11.17.0 14 / 1
11.16.0 14 / 1
11.15.24 14 / 1
11.15.22 14 / 1
11.15.21 14 / 1
11.15.20 14 / 1
11.15.19 14 / 1
11.15.18 14 / 1
11.15.17 14 / 1
11.15.16 14 / 1
11.15.15 14 / 1
11.15.14 14 / 1
11.15.13 14 / 1
11.15.12 14 / 1
11.15.11 14 / 1
11.15.10 14 / 1
11.15.9 14 / 1
11.15.8 14 / 1
11.15.7 14 / 1
11.15.6 14 / 1
11.15.5 14 / 1
11.15.4 14 / 1
11.15.3 14 / 1
11.15.2 14 / 1
11.15.1 14 / 1
11.15.0 14 / 1
11.14.2 14 / 1
11.14.1 14 / 1

v11.19.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.

v11.19.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.

v11.19.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.

v11.18.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.

v11.18.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.

v11.18.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.

v11.18.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.

v11.18.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.

v11.18.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.

v11.18.5

2 findings
HIGH Publisher changed: bitgobot → GitHub Actions (on 2026-04-28) provenance

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

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.

v11.18.4

2 findings
HIGH Publisher changed: bitgobot → GitHub Actions (on 2026-04-22) provenance

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

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.

v11.18.3

2 findings
HIGH Publisher changed: bitgobot → GitHub Actions (on 2026-04-14) provenance

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

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.

v11.18.2

2 findings
HIGH Publisher changed: bitgobot → GitHub Actions (on 2026-04-10) provenance

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

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.

v11.18.1

2 findings
HIGH Publisher changed: bitgobot → GitHub Actions (on 2026-04-08) provenance

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

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.

v11.18.0

2 findings
HIGH Publisher changed: bitgobot → GitHub Actions (on 2026-03-29) provenance

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.

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.

v11.17.8

2 findings
HIGH Publisher changed: bitgobot → GitHub Actions (on 2026-03-27) provenance

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.

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.

v11.17.7

2 findings
HIGH Publisher changed: bitgobot → GitHub Actions (on 2026-03-18) provenance

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.

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.

v11.17.6

2 findings
HIGH Publisher changed: bitgobot → GitHub Actions (on 2026-03-10) provenance

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.

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.

v11.17.5

1 finding
LOW No provenance attestation provenance

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

v11.17.4

1 finding
LOW No provenance attestation provenance

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

v11.17.3

1 finding
LOW No provenance attestation provenance

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

v11.17.2

1 finding
LOW No provenance attestation provenance

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

v11.17.1

1 finding
LOW No provenance attestation provenance

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

v11.17.0

1 finding
LOW No provenance attestation provenance

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

v11.16.0

1 finding
LOW No provenance attestation provenance

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

v11.15.24

1 finding
LOW No provenance attestation provenance

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

v11.15.22

1 finding
LOW No provenance attestation provenance

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

v11.15.21

1 finding
LOW No provenance attestation provenance

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

v11.15.20

1 finding
LOW No provenance attestation provenance

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

v11.15.19

1 finding
LOW No provenance attestation provenance

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

v11.15.18

1 finding
LOW No provenance attestation provenance

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

v11.15.17

1 finding
LOW No provenance attestation provenance

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

v11.15.16

1 finding
LOW No provenance attestation provenance

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

v11.15.15

1 finding
LOW No provenance attestation provenance

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

v11.15.14

1 finding
LOW No provenance attestation provenance

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

v11.15.13

1 finding
LOW No provenance attestation provenance

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

v11.15.12

1 finding
LOW No provenance attestation provenance

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

v11.15.11

1 finding
LOW No provenance attestation provenance

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

v11.15.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.

v11.15.9

3 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: zahin-mohammad → 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.

LOW No provenance attestation provenance

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

v11.15.8

2 findings
HIGH Publisher changed: zahin-mohammad → 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.

LOW No provenance attestation provenance

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

v11.15.7

2 findings
HIGH Publisher changed: zahin-mohammad → bitgobot (on 2025-10-21) provenance

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

v11.15.6

2 findings
HIGH Publisher changed: zahin-mohammad → bitgobot (on 2025-10-16) provenance

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

v11.15.5

2 findings
HIGH Publisher changed: zahin-mohammad → 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.

LOW No provenance attestation provenance

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

v11.15.4

2 findings
HIGH Publisher changed: zahin-mohammad → 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.

LOW No provenance attestation provenance

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

v11.15.3

2 findings
HIGH Publisher changed: zahin-mohammad → 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.

LOW No provenance attestation provenance

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

v11.15.2

2 findings
HIGH Publisher changed: zahin-mohammad → 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.

v11.15.1

2 findings
HIGH Publisher changed: zahin-mohammad → 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.

v11.15.0

2 findings
HIGH Publisher changed: zahin-mohammad → 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.

v11.14.2

2 findings
HIGH Publisher changed: zahin-mohammad → 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.

v11.14.1

1 finding
LOW No provenance attestation provenance

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