@bitgo/sdk-coin-lnbtc
BitGo SDK coin library for Lightning Bitcoin
Supply chain provenance
Status for the latest visible version.
Maintainers
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 | |
| publish-pattern | new-deps-added | AI (publish-pattern): @bitgo/statics is a first-party BitGo package; not a suspicious third-party dependency. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): bitgobot addition is part of BitGo's automated publish pipeline rollout. | ai | |
| maintainer-change | maintainer-takeover | AI (maintainer-change): BitGo org-wide consolidation to bitgobot publisher; consistent across 121 approved packages, not a hijack. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Removal of individual maintainers is part of BitGo's org-wide consolidation to bitgobot. | ai | |
| provenance | publisher-changed | AI (provenance): New publisher is a verified BitGo org account with strong track record; consistent with internal team account rotation. | ai | |
| dependencies | unvetted-dep:@bitgo/abstract-lightning | AI (dependencies): Internal BitGo monorepo dependency; expected and stable for this package. | ai | |
| dependencies | unvetted-dep:@bitgo/sdk-core | AI (dependencies): Internal BitGo monorepo dependency; expected and stable for this package. | ai |
Versions (showing 100 of 143)
| Version | Deps | Published |
|---|---|---|
| 1.8.24 | 4 / 2 | |
| 1.8.23 | 4 / 2 | |
| 1.8.21 | 4 / 2 | |
| 1.8.20 | 4 / 2 | |
| 1.8.19 | 4 / 2 | |
| 1.8.18 | 4 / 2 | |
| 1.8.17 | 4 / 2 | |
| 1.8.16 | 4 / 2 | |
| 1.8.15 | 4 / 2 | |
| 1.8.14 | 4 / 2 | |
| 1.8.13 | 4 / 2 | |
| 1.8.12 | 4 / 2 | |
| 1.8.11 | 4 / 2 | |
| 1.8.10 | 4 / 2 | |
| 1.8.9 | 4 / 2 | |
| 1.8.8 | 4 / 2 | |
| 1.8.7 | 4 / 2 | |
| 1.8.6 | 4 / 2 | |
| 1.8.5 | 4 / 2 | |
| 1.8.4 | 4 / 2 | |
| 1.8.3 | 4 / 2 | |
| 1.8.2 | 4 / 2 | |
| 1.8.1 | 4 / 2 | |
| 1.8.0 | 4 / 2 | |
| 1.7.1 | 4 / 2 | |
| 1.7.0 | 4 / 2 | |
| 1.6.9 | 4 / 2 | |
| 1.6.8 | 4 / 2 | |
| 1.6.7 | 3 / 2 | |
| 1.6.6 | 3 / 2 | |
| 1.6.5 | 3 / 2 | |
| 1.6.4 | 3 / 2 | |
| 1.6.3 | 3 / 2 | |
| 1.6.2 | 3 / 2 | |
| 1.6.1 | 3 / 2 | |
| 1.6.0 | 3 / 2 | |
| 1.5.25 | 3 / 2 | |
| 1.5.23 | 3 / 2 | |
| 1.5.22 | 3 / 2 | |
| 1.5.21 | 3 / 2 | |
| 1.5.20 | 3 / 2 | |
| 1.5.19 | 3 / 2 | |
| 1.5.18 | 3 / 2 | |
| 1.5.17 | 3 / 2 | |
| 1.5.16 | 3 / 2 | |
| 1.5.15 | 3 / 2 | |
| 1.5.14 | 3 / 2 | |
| 1.5.13 | 3 / 2 | |
| 1.5.12 | 3 / 2 | |
| 1.5.11 | 3 / 2 | |
| 1.5.10 | 3 / 2 | |
| 1.5.9 | 3 / 2 | |
| 1.5.8 | 3 / 2 | |
| 1.5.7 | 3 / 2 | |
| 1.5.6 | 3 / 2 | |
| 1.5.5 | 3 / 2 | |
| 1.5.4 | 3 / 2 | |
| 1.5.3 | 3 / 2 | |
| 1.5.2 | 3 / 2 | |
| 1.5.1 | 3 / 2 | |
| 1.5.0 | 3 / 2 | |
| 1.4.4 | 3 / 2 | |
| 1.4.3 | 3 / 2 | |
| 1.4.2 | 3 / 2 | |
| 1.4.1 | 3 / 2 | |
| 1.4.0 | 3 / 2 | |
| 1.3.15 | 3 / 2 | |
| 1.3.14 | 3 / 2 | |
| 1.3.13 | 3 / 2 | |
| 1.3.12 | 3 / 2 | |
| 1.3.11 | 3 / 2 | |
| 1.3.10 | 3 / 2 | |
| 1.3.9 | 3 / 2 | |
| 1.3.8 | 3 / 2 | |
| 1.3.7 | 3 / 2 | |
| 1.3.6 | 3 / 2 | |
| 1.3.5 | 3 / 2 | |
| 1.3.4 | 3 / 2 | |
| 1.3.3 | 3 / 2 | |
| 1.3.2 | 3 / 2 | |
| 1.3.1 | 3 / 2 | |
| 1.3.0 | 3 / 2 | |
| 1.2.14 | 3 / 2 | |
| 1.2.13 | 3 / 2 | |
| 1.2.12 | 3 / 2 | |
| 1.2.11 | 3 / 2 | |
| 1.2.10 | 3 / 2 | |
| 1.2.9 | 3 / 2 | |
| 1.2.8 | 3 / 2 | |
| 1.2.7 | 3 / 2 | |
| 1.2.6 | 3 / 2 | |
| 1.2.5 | 3 / 2 | |
| 1.2.4 | 3 / 2 | |
| 1.2.3 | 3 / 2 | |
| 1.2.2 | 3 / 2 | |
| 1.2.1 | 3 / 2 | |
| 1.2.0 | 3 / 2 | |
| 1.1.46 | 3 / 2 | |
| 1.1.45 | 3 / 2 | |
| 1.1.44 | 3 / 2 |
v1.8.24
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.8.23
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.8.21
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.8.20
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.8.19
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.8.18
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.2.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.46
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.45
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.44
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.