← Home

events

npm Repository Homepage

Node's event emitter for all engines.

17
Versions
MIT
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

gozalagoto-bus-stopdefunctzombie

Keywords

eventseventEmittereventDispatcherlisteners

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Legitimate maintainer transition to goto-bus-stop (2018), who has extensive npm track record (1228 approved packages). ai
maintainer-change maintainer-added AI (maintainer-change): goto-bus-stop is a well-established npm publisher added as maintainer in a legitimate handoff. ai
provenance no-provenance AI (provenance): Published in 2018 before Sigstore provenance was available; not a risk signal for this package. ai

Versions (showing 17 of 17)

Version Deps Published
3.3.0 0 / 6
3.2.0 0 / 5
3.1.0 0 / 3
3.0.0 0 / 3
2.1.0 0 / 4
2.0.0 0 / 4
1.1.1 0 / 2
1.1.0 0 / 2
1.0.2 0 / 2
1.0.1 0 / 2
1.0.0 0 / 2
0.5.0 0 / 1
0.4.0 1 / 1
0.3.0 1 / 1
0.2.0 1 / 1
0.1.1 1 / 1
0.1.0 1 / 1

v3.2.0

1 finding
LOW No provenance attestation provenance

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

v2.1.0

2 findings
HIGH Publisher changed: defunctzombie → goto-bus-stop (on 2018-05-25) provenance

This version was published by a different npm account than previous versions on 2018-05-25. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v2.0.0

2 findings
HIGH Publisher changed: defunctzombie → goto-bus-stop (on 2018-02-02) provenance

This version was published by a different npm account than previous versions on 2018-02-02. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v1.0.1

1 finding
LOW No provenance attestation provenance

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