All @cleocode/contracts versions
@cleocode/contracts @2026.4.13
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
0
Dependencies
0
Dev Dependencies
112.9 KB
Package Size
Published
Domain types, interfaces, and contracts for the CLEO ecosystem
Maintainers
kryptobaseddev
Risk Dispositions (2 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): Provenance regression is a strong supply-chain compromise indicator for this package; should fail every version that lacks attestation after prior versions had it. | |
publisher-changed |
provenance | reject | AI | AI (provenance): Publisher changed from GitHub Actions to a human account coinciding with provenance regression; warrants rejection until legitimacy is confirmed. |
SAST Findings (2)
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.
HIGH
Publisher changed: GitHub Actions → kryptobaseddev (on 2026-04-09)
provenance
This version was published by a different npm account than previous versions on 2026-04-09. This could indicate a legitimate maintainer transition or an account compromise.
Review Summary
Risk score: 25. Findings: 1 high (+25), 1 info (+0).
Published to npm: