@cleocode/agents @2026.4.0
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.
50
Risk Score
MIT
License
No
Install Scripts
0
Dependencies
0
Dev Dependencies
8.9 KB
Package Size
Published
CLEO agent protocols and templates
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): Loss of provenance attestation after a history of CI/CD-attested publishes is a strong supply-chain compromise indicator; this judgment generalizes until provenance is restored. | |
publisher-changed |
provenance | reject | AI | AI (provenance): Publisher change from GitHub Actions to a human account, coinciding with dropped provenance, is a high-risk pattern consistent with account compromise. |
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-01)
provenance
This version was published by a different npm account than previous versions on 2026-04-01. This could indicate a legitimate maintainer transition or an account compromise.
Review Summary
Risk score: 50. Findings: 2 high (+50).
Published to npm: