← Home

@bitgo/unspents

npm Repository Homepage
54
Versions
—
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

Keywords

bitcoinutxo

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): BitGo migrated publishing to GitHub Actions CI/CD; SLSA attestation confirms legitimate automated pipeline. ai
publish-pattern dormant-publish AI (publish-pattern): Dormancy reflects monorepo release cadence, not account takeover; SLSA provenance and org continuity confirm legitimacy. ai
phantom-deps phantom-dep:lodash AI (phantom-deps): lodash is a declared runtime dependency; phantom-dep heuristic false positive for this package. ai

Versions (showing 54 of 54)

Version Deps Published
0.51.7 4 / 4
0.51.6 4 / 4
0.51.5 4 / 4
0.51.4 4 / 4
0.51.3 4 / 4
0.51.2 4 / 4
0.51.1 4 / 4
0.51.0 4 / 4
0.50.14 4 / 4
0.50.13 4 / 4
0.50.12 4 / 4
0.50.11 4 / 4
0.50.10 4 / 4
0.50.9 4 / 4
0.50.8 4 / 4
0.50.7 4 / 4
0.50.6 4 / 4
0.50.5 4 / 4
0.50.4 4 / 4
0.50.3 4 / 4
0.50.2 4 / 4
0.50.1 4 / 4
0.50.0 4 / 4
0.49.0 4 / 4
0.48.9 4 / 4
0.48.8 4 / 4
0.48.7 4 / 4
0.48.6 4 / 4
0.48.5 4 / 4
0.48.4 4 / 4
0.48.3 4 / 4
0.48.2 4 / 4
0.48.1 4 / 4
0.48.0 4 / 4
0.47.21 4 / 4
0.47.20 4 / 4
0.47.19 4 / 4
0.47.18 4 / 4
0.47.17 4 / 4
0.47.16 4 / 4
0.47.15 4 / 4
0.47.14 4 / 4
0.47.13 4 / 4
0.47.12 4 / 4
0.47.11 4 / 4
0.47.10 4 / 4
0.47.9 4 / 4
0.47.8 4 / 4
0.47.7 4 / 4
0.47.6 4 / 4
0.47.5 4 / 4
0.47.4 4 / 4
0.47.3 4 / 4
0.47.2 4 / 4

v0.51.7

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.47.21

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: margueriteblair → mohammadalfaiyaz_bitgo (on 2025-04-04, known maintainer) provenance

This version was published by a different npm account (mohammadalfaiyaz_bitgo) than the most recent previously approved version (margueriteblair) on 2025-04-04, but mohammadalfaiyaz_bitgo is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v0.47.20

1 finding
LOW No provenance attestation provenance

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

v0.47.19

1 finding
LOW No provenance attestation provenance

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

v0.47.18

1 finding
LOW No provenance attestation provenance

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

v0.47.17

1 finding
LOW No provenance attestation provenance

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

v0.47.16

1 finding
LOW No provenance attestation provenance

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

v0.47.15

1 finding
LOW No provenance attestation provenance

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

v0.47.14

1 finding
LOW No provenance attestation provenance

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

v0.47.13

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: alebusse → margueriteblair (on 2024-11-14, known maintainer) provenance

This version was published by a different npm account (margueriteblair) than the most recent previously approved version (alebusse) on 2024-11-14, but margueriteblair is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v0.47.12

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: pengyuc_bitgo → alebusse (on 2024-11-01, known maintainer) provenance

This version was published by a different npm account (alebusse) than the most recent previously approved version (pengyuc_bitgo) on 2024-11-01, but alebusse is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v0.47.11

1 finding
LOW No provenance attestation provenance

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

v0.47.10

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: margueriteblair → pengyuc_bitgo (on 2024-09-03, known maintainer) provenance

This version was published by a different npm account (pengyuc_bitgo) than the most recent previously approved version (margueriteblair) on 2024-09-03, but pengyuc_bitgo is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v0.47.9

1 finding
LOW No provenance attestation provenance

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

v0.47.8

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: mohammadalfaiyaz_bitgo → margueriteblair (on 2024-08-07, known maintainer) provenance

This version was published by a different npm account (margueriteblair) than the most recent previously approved version (mohammadalfaiyaz_bitgo) on 2024-08-07, but margueriteblair is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v0.47.7

1 finding
LOW No provenance attestation provenance

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

v0.47.6

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: alebusse → mohammadalfaiyaz_bitgo (on 2024-07-04, known maintainer) provenance

This version was published by a different npm account (mohammadalfaiyaz_bitgo) than the most recent previously approved version (alebusse) on 2024-07-04, but mohammadalfaiyaz_bitgo is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v0.47.5

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: pengyuc_bitgo → alebusse (on 2024-06-26, known maintainer) provenance

This version was published by a different npm account (alebusse) than the most recent previously approved version (pengyuc_bitgo) on 2024-06-26, but alebusse is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v0.47.4

1 finding
LOW No provenance attestation provenance

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

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

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