← Home

@bitgo-beta/unspents

Defines the chain codes used for different unspent types and methods to calculate bitcoin transaction sizes

3
Versions
Apache-2.0
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

bitgobotbitgoaaron

Keywords

bitcoinutxo

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:lodash AI (phantom-deps): lodash is a declared runtime dependency in package.json; phantom-dep false positive for this package. ai
provenance no-provenance AI (provenance): BitGo monorepo package; no-provenance is common and not a risk signal here. ai

Versions (showing 3 of 3)

Version Deps Published
0.13.1 4 / 4
0.11.2 4 / 4
0.8.3 4 / 4

v0.13.1

2 findings
MEDIUM Publisher changed: bitgoaaron → bitgobot (on 2023-05-22, unremoved on npm for 1158d) provenance

This version was published by a different npm account (bitgobot) than the most recent previously approved version (bitgoaaron) on 2023-05-22. It has since remained available on npm for 1158 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

INFO No provenance attestation provenance

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

v0.11.2

2 findings
MEDIUM Publisher changed: bitgoaaron → bitgobot (on 2022-11-03, unremoved on npm for 1358d) provenance

This version was published by a different npm account (bitgobot) than the most recent previously approved version (bitgoaaron) on 2022-11-03. It has since remained available on npm for 1358 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

INFO No provenance attestation provenance

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