@noble/secp256k1 @1.7.2
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.
40
Risk Score
MIT
License
No
Install Scripts
0
Dependencies
12
Dev Dependencies
27.8 KB
Package Size
Published
Fastest 5KB JS implementation of secp256k1 ECDH & ECDSA signatures compliant with RFC6979
Maintainers
paulmillr
Keywords
secp256k1secpsecp256ellipticelliptic curvecurvesignatureeccrfc6979schnorrsigbip0340bip340ecdsaendomorphismcryptographysecuritynoble
Dev Dependencies (12)
| Package | Constraint | Registry Status |
|---|---|---|
| jest | 28.1.0 | auto_approved |
| rollup | 2.75.5 | auto_approved |
| ts-jest | 28.0.4 | auto_approved |
| prettier | 2.6.2 | auto_approved |
| fast-check | 3.0.0 | No greenflagged match |
| typescript | 4.7.3 | auto_approved |
| @types/jest | 28.1.1 | No greenflagged match |
| @types/node | 17.0.18 | auto_approved |
| micro-bmark | 0.2.0 | Not imported |
| @noble/hashes | 1.1.2 | auto_approved |
| @rollup/plugin-commonjs | 22.0.0 | auto_approved |
| @rollup/plugin-node-resolve | 13.3.0 | auto_approved |
Changes from v2.2.3
Dependency Changes
Script Changes
+ lint+ format+ coverage - loc- build:min- build:mingz- test:webcryptoFile Changes
4 added
3 removed
2 modified
size delta: +26.1 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): Cryptographic primitive losing provenance attestation is a critical supply-chain risk; this pattern should fail every version of this package until attestation is restored. |
SAST Findings (1)
CRITICAL
Provenance attestation missing — previous versions had it
provenance
[Always reject] 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: 40. Findings: 1 critical (+40).
Commit: 14aa2cdd265b Browse source
Published to npm: