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.
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): Provenance regression on a package that previously used CI/CD attestations is a strong compromise indicator; generalizes until CI publishing is restored.
SAST Findings (6)
HIGHProvenance attestation missing — previous versions had itprovenance
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.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
INFOPublisher changed: GitHub Actions → ehindero (on 2026-06-17, known maintainer)provenance
This version was published by a different npm account (ehindero) than the most recent previously approved version (GitHub Actions) on 2026-06-17, but ehindero is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
Review Summary
Risk score: 100 (capped from 158). Findings: 5 high (+125), 3 medium (+30), 1 low (+3), 3 info (+0).