fbemitter
Facebook's EventEmitter is a simple emitter implementation that prioritizes speed and simplicity. It is conceptually similar to other emitters like Node's EventEmitter, but the precise APIs differ. More complex abstractions like the event systems used on
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): Publisher change from kyldvs to zpao occurred in Jan 2016 — a legitimate Facebook internal transition. zpao is a well-established Meta/Facebook engineer with strong track record. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): fb and zpao are official Facebook/Meta npm accounts. This is a legitimate organizational maintainer setup, not a compromise. | ai | |
| bogus-package | bogus-package | AI (bogus-package): The spam-publisher flag on 'fb' and 'zpao' are legitimate Facebook/Meta npm org accounts, not spam. This is a stable false positive for this package. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 3.0.0 | 1 / 9 | |
| 2.1.1 | 1 / 9 | |
| 2.1.0 | 1 / 9 | |
| 2.0.3 | 1 / 9 | |
| 2.0.2 | 1 / 9 | |
| 2.0.1 | 1 / 9 | |
| 2.0.0 | 1 / 8 |
v3.0.0
2 findingsThis version was published by a different npm account than previous versions on 2021-01-09. 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.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1
2 findingsThis version was published by a different npm account than previous versions on 2016-01-03. 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.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.