reportback
Somewhere between a stream, a switchback, a logger, and an EventEmitter.
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): rachaelshaw is a known Sails.js core team member with 750 approved packages; transition from mikermcneil is a legitimate organizational handoff within the same ecosystem. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): rachaelshaw is a well-established npm publisher (750 approved packages) and known Sails.js contributor; addition is a legitimate team transition. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Removal of particlebanana is consistent with the known Sails.js team restructuring; no malicious indicators present. | ai |
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 2.0.2 | 2 / 0 | |
| 2.0.1 | 2 / 0 | |
| 0.1.9 | 4 / 0 | |
| 0.1.8 | 4 / 0 | |
| 0.1.7 | 4 / 0 | |
| 0.1.6 | 4 / 0 | |
| 0.1.5 | 4 / 0 | |
| 0.1.4 | 4 / 0 | |
| 0.1.3 | 5 / 0 | |
| 0.1.2 | 5 / 0 | |
| 0.1.1 | 5 / 0 | |
| 0.1.0 | 4 / 0 |
v2.0.2
2 findingsThis version was published by a different npm account than previous versions on 2019-04-17. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.