All @effectstream/bitcoin-contracts versions

@effectstream/bitcoin-contracts @0.100.15

rejected
This version was rejected. It did not pass GreenFlagged's security review and is not served by the registry. The findings and risk dispositions below explain why.
43
Risk Score
MIT
License
No
Install Scripts
3
Dependencies
0
Dev Dependencies
3.7 KB
Package Size
Published

Bitcoin script utilities for EffectStream

Maintainers

edwarddc

Dependencies (3)

PackageConstraintRegistry Status
ecpair ^3.0.0 auto_approved
bitcoinjs-lib ^7.0.0 auto_approved
tiny-secp256k1 ^2.2.4 auto_approved

Transitive Dependency Tree

12 transitive deps max depth 5
  ├─ bitcoinjs-lib ^7.0.0 → 7.0.1
  ├─ ecpair ^3.0.0 → 3.0.0
├─ tiny-secp256k1 ^2.2.4 → 2.2.4
  ├─ @noble/hashes ^1.2.0 → 1.8.0
  ├─ bech32 ^2.0.0 → 2.0.0
  ├─ bs58check ^4.0.0 → 4.0.0
  ├─ uint8array-tools 0.0.7 → 0.0.7
  ├─ uint8array-tools ^0.0.8 → 0.0.8
  ├─ uint8array-tools ^0.0.9 → 0.0.9
  ├─ valibot ^0.37.0
  ├─ valibot ^1.2.0 → 1.4.1
  ├─ varuint-bitcoin ^2.0.0
├─ wif ^5.0.0 → 5.0.0
  ├─ @noble/hashes ^1.2.0 → 1.8.0
  ├─ bs58 ^6.0.0 → 6.0.0
├─ bs58check ^4.0.0 → 4.0.0
  ├─ @noble/hashes ^1.2.0 → 1.8.0
  ├─ base-x ^5.0.0 → 5.0.1
├─ bs58 ^6.0.0 → 6.0.0
  ├─ base-x ^5.0.0 → 5.0.1

Changes from v0.100.14

No metadata changes detected.

File Changes

1 added 0 removed 1 modified size delta: +2.4 KB

Risk Dispositions (1 applicable to this version, 1 other)

Accepted rules are downgraded to INFO on future analyses; rejected rules escalate to CRITICAL.

Rule Source Disposition Author Reason
bogus-package bogus-package reject AI AI (bogus-package): Both maintainers flagged as spam; stable reject signal for this package.
Show 1 disposition(s) that do not match any finding on this version
Rule Source Disposition Author Reason
publisher-changed provenance reject AI AI (provenance): New publisher eduardosoto is SPAM-FLAGGED; publisher change to a spam actor generalizes across versions.

SAST Findings (1)

LOW No provenance attestation provenance

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

Review Summary

Risk score: 43. Findings: 1 critical (+40), 1 low (+3), 5 info (+0).

Published to npm: