@bitgo/sdk-coin-lnbtc MIT 43 versions

@bitgo/sdk-coin-lnbtc

npm Repository Homepage

BitGo SDK coin library for Lightning Bitcoin

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.

Source	Rule	Reason	Accepted by	When
source-diff	obfuscated-file:dist/test/unit/index.js	AI (source-diff): File is standard TypeScript-compiled CommonJS output, not obfuscated; long lines are from bundled test fixtures.	ai	2026/05/17
publish-pattern	new-deps-added	AI (publish-pattern): @bitgo/statics is a first-party BitGo package; not a suspicious third-party dependency.	ai	2026/05/17
maintainer-change	maintainer-added	AI (maintainer-change): bitgobot addition is part of BitGo's automated publish pipeline rollout.	ai	2026/05/17
maintainer-change	maintainer-takeover	AI (maintainer-change): BitGo org-wide consolidation to bitgobot publisher; consistent across 121 approved packages, not a hijack.	ai	2026/05/17
maintainer-change	maintainer-removed	AI (maintainer-change): Removal of individual maintainers is part of BitGo's org-wide consolidation to bitgobot.	ai	2026/05/17
provenance	publisher-changed	AI (provenance): New publisher is a verified BitGo org account with strong track record; consistent with internal team account rotation.	ai	2026/05/17
dependencies	unvetted-dep:@bitgo/abstract-lightning	AI (dependencies): Internal BitGo monorepo dependency; expected and stable for this package.	ai	2026/05/17
dependencies	unvetted-dep:@bitgo/sdk-core	AI (dependencies): Internal BitGo monorepo dependency; expected and stable for this package.	ai	2026/05/17

Versions (showing 43 of 143)

Version	Deps	Published
1.1.43	3 / 2	2025-02-11
1.1.42	3 / 2	2025-02-05
1.1.41	3 / 2	2025-01-28
1.1.40	3 / 2	2025-01-23
1.1.39	3 / 2	2025-01-23
1.1.38	3 / 2	2025-01-20
1.1.37	3 / 2	2025-01-15
1.1.36	3 / 2	2025-01-09
1.1.35	3 / 2	2025-01-03
1.1.34	3 / 2	2024-12-24
1.1.33	3 / 2	2024-12-19
1.1.32	3 / 2	2024-12-17
1.1.30	3 / 2	2024-12-12
1.1.29	3 / 2	2024-12-11
1.1.28	3 / 2	2024-12-03
1.1.27	3 / 2	2024-11-26
1.1.26	3 / 2	2024-11-21
1.1.25	3 / 2	2024-11-19
1.1.24	3 / 2	2024-11-14
1.1.23	3 / 2	2024-11-08
1.1.22	3 / 2	2024-11-07
1.1.21	3 / 2	2024-11-01
1.1.20	3 / 2	2024-10-22
1.1.19	3 / 2	2024-10-15
1.1.18	3 / 2	2024-10-08
1.1.17	3 / 2	2024-10-04
1.1.16	3 / 2	2024-09-24
1.1.15	3 / 2	2024-09-19
1.1.14	3 / 2	2024-09-16
1.1.13	3 / 2	2024-09-10
1.1.12	3 / 2	2024-09-03
1.1.11	3 / 2	2024-08-29
1.1.10	3 / 2	2024-08-27
1.1.9	3 / 2	2024-08-20
1.1.8	3 / 2	2024-08-13
1.1.7	3 / 2	2024-08-07
1.1.6	3 / 2	2024-07-30
1.1.5	3 / 2	2024-07-24
1.1.4	3 / 2	2024-07-16
1.1.3	3 / 2	2024-07-04
1.1.2	3 / 2	2024-07-02
1.1.1	3 / 2	2024-06-27
1.1.0	3 / 2	2024-06-26

v1.1.43

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

v1.1.18

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

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

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

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

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

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

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

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

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

v1.1.8

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

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

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

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

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