← Home

emitter-component

npm Repository Homepage

Event emitter

12
Versions
—
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

corehswatinemanthonyshortianstormtaylorcristiandoucestagasrauchgkelonyeamasadjuliangruberdominicbarnesmattmuellertootallnateyieldsretrofoxsindresorhustjholowaychukjonathanongjongleberryforbeslindesaycalvinfodefunctzombie

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Documented legitimate transfer to sindresorhus, a highly trusted npm publisher. Repo URL confirms ownership. Verdict generalizes to future versions. ai
maintainer-change maintainer-added AI (maintainer-change): Large maintainer list addition reflects legitimate community/org transfer to sindresorhus's stewardship. No malicious indicators. ai
provenance no-provenance AI (provenance): Established package without Sigstore provenance; low risk given publisher trust level and package age. ai

Versions (showing 12 of 12)

Version Deps Published
2.0.0 0 / 2
1.1.2 0 / 2
1.1.1 0 / 2
1.1.0 1 / 2
1.0.1 1 / 2
1.0.0 0 / 2
0.0.6 0 / 2
0.0.5 0 / 2
0.0.4 0 / 2
0.0.3 0 / 2
0.0.2 0 / 2
0.0.1 0 / 2

v2.0.0

1 finding
LOW No provenance attestation provenance

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

v1.1.2

2 findings
HIGH Publisher changed: tjholowaychuk → sindresorhus (on 2023-11-16) provenance

This version was published by a different npm account than previous versions on 2023-11-16. 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.1.1

1 finding
LOW No provenance attestation provenance

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

v1.1.0

1 finding
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.

v1.0.0

1 finding
LOW No provenance attestation provenance

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

v0.0.6

1 finding
LOW No provenance attestation provenance

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