All @effectstream/npm-avail-node versions

@effectstream/npm-avail-node @0.100.17

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
ISC
License
No
Install Scripts
2
Dependencies
0
Dev Dependencies
4.1 KB
Package Size
Published

A wrapper for the Avail node binary

Maintainers

edwarddc

Dependencies (2)

PackageConstraintRegistry Status
tar ^6.2.0 No greenflagged match
linus ^0.0.6 auto_approved

Transitive Dependency Tree

5 transitive deps max depth 2
  ├─ linus ^0.0.6 → 0.0.6
├─ tar ^6.2.0
  ├─ getos ^1.0.1
  ├─ memorize 0.0.4 → 0.0.4
  ├─ whenever 0.0.2 → 0.0.2

Changes from v0.100.10

No metadata changes detected.

File Changes

1 added 0 removed 1 modified size delta: +1.6 KB

Risk Dispositions (1 applicable to this version, 1 other)

Accepted rules are downgraded to INFO on future analyses; rejected rules escalate to CRITICAL.

Rule Source Disposition Author Reason
bogus-package bogus-package reject AI AI (bogus-package): Both maintainers flagged as spam; stable reject signal for this package.
Show 1 disposition(s) that do not match any finding on this version
Rule Source Disposition Author Reason
publisher-changed provenance reject AI AI (provenance): New publisher is SPAM-FLAGGED; takeover pattern generalizes to all future versions from this publisher.

SAST Findings (1)

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

Review Summary

Risk score: 40. Findings: 1 critical (+40), 4 info (+0).

Published to npm: