bare-events
Event emitters for JavaScript
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Moved to GitHub Actions CI/CD publishing with SLSA provenance; same org repo. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): kasperisager replaced by GitHub Actions CI/CD; same holepunchto org. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 2.8.3 | 0 / 6 | |
| 2.8.2 | 0 / 5 | |
| 2.8.1 | 0 / 5 | |
| 2.8.0 | 0 / 5 | |
| 2.7.0 | 0 / 3 | |
| 2.6.1 | 0 / 3 | |
| 2.6.0 | 0 / 3 | |
| 2.4.2 | 0 / 2 |
v2.8.3
2 findingsThis version was published by a different npm account than previous versions on 2026-05-14. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.8.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.