@scure/bip32 @1.6.1
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.
25
Risk Score
MIT
License
No
Install Scripts
3
Dependencies
4
Dev Dependencies
12.6 KB
Package Size
Published
Secure, audited & minimal implementation of BIP32 hierarchical deterministic (HD) wallets over secp256k1
Maintainers
paulmillr
Keywords
bip32hierarchicaldeterministichd keybip0032bip-32bip39microscuremnemonicphrasecode
Dependencies (3)
| Package | Constraint | Registry Status |
|---|---|---|
| @scure/base | ~1.2.1 | auto_approved |
| @noble/curves | ~1.8.0 | auto_approved |
| @noble/hashes | ~1.7.0 | auto_approved |
Dev Dependencies (4)
| Package | Constraint | Registry Status |
|---|---|---|
| prettier | 3.3.2 | auto_approved |
| typescript | 5.5.2 | auto_approved |
| micro-should | 0.4.0 | Not imported |
| @paulmillr/jsbt | 0.2.1 | Not imported |
Transitive Dependency Tree
3 transitive deps
max depth 2
├─
@noble/curves
~1.8.0
→ 1.8.2
├─
@noble/hashes
~1.7.0
→ 1.7.2
├─
@scure/base
~1.2.1
→ 1.2.6
├─
@noble/hashes
1.7.2
→ 1.7.2
Changes from v1.6.0
Dependency Changes
| Change | Package | Version |
|---|---|---|
| changed | @noble/curves | ~1.7.0 → ~1.8.0 |
| changed | @noble/hashes | ~1.6.0 → ~1.7.0 |
File Changes
0 added
0 removed
9 modified
size delta: +1.6 KB
Risk Dispositions (1 applicable to this version, 0 other)
Accepted rules are downgraded to INFO on future analyses; rejected rules escalate to CRITICAL.
| Rule | Source | Disposition | Author | Reason | |
|---|---|---|---|---|---|
regressed-provenance |
provenance | reject | AI | AI (provenance): Security-critical crypto package; provenance regression is a strong supply-chain compromise signal. Publisher must restore CI/CD attestation before any version is admitted. |
SAST Findings (1)
HIGH
Provenance attestation missing — previous versions had it
provenance
This version was published without provenance, but prior versions were published via CI/CD with attestations. This is a strong signal of a potential account compromise or unauthorized publish. The axios attack (March 2026) exhibited exactly this pattern.
Review Summary
Risk score: 25. Findings: 1 high (+25).
Commit: bc83675aca84 Browse source
Published to npm: