← Home

@bitgo/sdk-coin-xlm

BitGo SDK coin library for Xlm

100
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-removed AI (maintainer-change): Mass removal of individual BitGo maintainers consistent with org-wide bot-publisher migration. ai
maintainer-change maintainer-added AI (maintainer-change): bitgobot addition is part of BitGo org-wide automation rollout, not a takeover. ai
provenance publisher-changed AI (provenance): BitGo org-wide migration to bitgobot publisher; consistent across many approved packages. ai
phantom-deps phantom-dep:stellar-sdk AI (phantom-deps): Declared runtime dep; phantom-dep heuristic fires on indirect usage patterns. ai
phantom-deps phantom-dep:bignumber.js AI (phantom-deps): Declared runtime dep; phantom-dep heuristic fires on indirect usage patterns. ai
phantom-deps phantom-dep:@bitgo/sdk-core AI (phantom-deps): Same-org declared dep; stable false positive for this monorepo package. ai
phantom-deps phantom-dep:@bitgo/statics AI (phantom-deps): Same-org declared dep; stable false positive for this monorepo package. ai
phantom-deps phantom-dep:lodash AI (phantom-deps): Declared runtime dep in BitGo monorepo; phantom-dep heuristic fires on indirect usage patterns. ai
phantom-deps phantom-dep:superagent AI (phantom-deps): Declared runtime dep; phantom-dep heuristic fires on indirect usage patterns. ai
provenance no-provenance AI (provenance): BitGo SDK packages consistently lack Sigstore provenance; stable false positive for this package family. ai
dependencies unvetted-dep:@bitgo/sdk-core AI (dependencies): First-party BitGo monorepo package; stable false positive for this package family. ai

Versions (showing 100 of 133)

Version Deps Published
3.10.3 6 / 2
3.10.2 6 / 2
3.10.1 6 / 2
3.10.0 6 / 2
3.9.9 6 / 2
3.9.8 6 / 2
3.9.7 6 / 2
3.9.6 6 / 2
3.9.5 6 / 2
3.9.4 6 / 2
3.9.3 6 / 2
3.9.2 6 / 2
3.9.1 6 / 2
3.9.0 6 / 2
3.8.9 6 / 2
3.8.8 6 / 2
3.8.7 6 / 2
3.8.6 6 / 2
3.8.5 6 / 2
3.8.4 6 / 2
3.8.3 6 / 2
3.8.2 6 / 2
3.8.1 6 / 2
3.8.0 6 / 2
3.7.22 6 / 2
3.7.20 6 / 2
3.7.19 6 / 2
3.7.18 6 / 2
3.7.17 6 / 2
3.7.16 6 / 2
3.7.15 6 / 2
3.7.14 6 / 2
3.7.13 6 / 2
3.7.12 6 / 2
3.7.11 6 / 2
3.7.10 6 / 2
3.7.0 6 / 2
3.6.1 6 / 2
3.6.0 6 / 2
3.5.4 6 / 2
3.5.3 6 / 2
3.5.2 6 / 2
3.5.1 6 / 2
3.5.0 6 / 2
3.4.15 6 / 2
3.4.14 6 / 2
3.4.13 6 / 2
3.4.12 6 / 2
3.4.11 6 / 2
3.4.10 6 / 2
3.4.9 6 / 2
3.4.8 6 / 2
3.4.7 6 / 2
3.4.6 6 / 2
3.4.5 6 / 2
3.4.4 6 / 2
3.4.3 6 / 2
3.4.2 6 / 2
3.4.1 6 / 2
3.4.0 6 / 2
3.3.0 6 / 2
3.2.56 6 / 2
3.2.55 6 / 2
3.2.54 6 / 2
3.2.53 6 / 2
3.2.52 6 / 2
3.2.51 6 / 2
3.2.50 6 / 2
3.2.49 6 / 2
3.2.48 6 / 2
3.2.47 6 / 2
3.2.46 6 / 2
3.2.45 6 / 2
3.2.44 6 / 2
3.2.43 6 / 2
3.2.42 6 / 2
3.2.41 6 / 2
3.2.40 6 / 2
3.2.39 6 / 2
3.2.38 6 / 2
3.2.37 6 / 2
3.2.36 6 / 2
3.2.35 6 / 2
3.2.34 6 / 2
3.2.33 6 / 2
3.2.32 6 / 2
3.2.31 6 / 2
3.2.30 6 / 2
3.2.29 6 / 2
3.2.28 6 / 2
3.2.26 6 / 2
3.2.25 6 / 2
3.2.24 6 / 2
3.2.23 6 / 2
3.2.22 6 / 2
3.2.21 6 / 2
3.2.20 6 / 2
3.2.19 6 / 2
3.2.18 6 / 2
3.2.17 6 / 2
Showing 100 of 133 Next page →

v3.2.51

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.2.50

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.2.49

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.2.48

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.2.47

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.2.46

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.2.45

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.2.44

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.2.43

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.2.42

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.2.41

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.2.40

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.2.39

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.2.38

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.2.37

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.2.36

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.2.35

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.2.34

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.2.33

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.2.32

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.2.31

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.2.30

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.2.29

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.2.28

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.2.26

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.2.25

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.2.24

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.2.23

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.2.22

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.2.21

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.2.20

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.2.19

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.2.18

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.2.17

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.