← Home

@bitgo/abstract-substrate

npm Repository Homepage

BitGo SDK coin library for Substrate base implementation

6
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): BitGo consolidated publishing to bitgobot across their entire SDK; not a hostile takeover. ai
maintainer-change maintainer-added AI (maintainer-change): bitgobot is BitGo's publishing bot; addition is expected across all BitGo SDK packages. ai
maintainer-change maintainer-removed AI (maintainer-change): Removal of individual maintainers in favor of bitgobot is an org-wide BitGo policy change. ai
provenance publisher-changed AI (provenance): zahin-mohammad is an established BitGo org publisher with 63 approved packages; transition appears legitimate. 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 6 of 106)

Version Deps Published
1.1.3 12 / 0
1.1.2 12 / 0
1.1.1 12 / 0
1.1.0 12 / 0
1.0.2 2 / 0
1.0.1 2 / 0

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

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

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

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

v1.0.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.

v1.0.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.