@noble/curves @2.0.0-beta.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
1
Dependencies
7
Dev Dependencies
294.4 KB
Package Size
Published
Audited & minimal JS implementation of elliptic curve cryptography
Maintainers
paulmillr
Keywords
ellipticcurvecryptographysecp256k1ed25519p256p384p521secp256r1ed448x25519ed25519bls12-381bn254alt_bn128blsnobleeccecdsaeddsaweierstrassmontgomeryedwardsschnorrfft
Dependencies (1)
| Package | Constraint | Registry Status |
|---|---|---|
| @noble/hashes | 2.0.0-beta.3 | auto_approved |
Dev Dependencies (7)
| Package | Constraint | Registry Status |
|---|---|---|
| prettier | 3.5.3 | auto_approved |
| fast-check | 4.1.1 | auto_approved |
| typescript | 5.8.3 | auto_approved |
| @types/node | 22.15.21 | auto_approved |
| micro-bmark | 0.4.2 | Not imported |
| micro-should | 0.5.3 | Not imported |
| @paulmillr/jsbt | 0.4.0 | Not imported |
Transitive Dependency Tree
1 transitive deps
max depth 1
├─
@noble/hashes
2.0.0-beta.3
→ 2.0.0-beta.3
Changes from v1.9.6
Dependency Changes
| Change | Package | Version |
|---|---|---|
| changed | @noble/hashes | 1.8.0 → 2.0.0-beta.3 |
File Changes
10 added
113 removed
87 modified
size delta: -780.3 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 library; provenance regression is a strong supply chain risk signal. All future versions should have CI/CD attestations matching prior versions. |
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), 2 info (+0).
Commit: 289db6f25979 Browse source
Published to npm: