← Home

add-dom-event-listener

npm Repository Homepage

add dom event listener. normalize ie and others

5
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

yiminghe

Keywords

domeventie

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
npm-metadata suspicious-initial-version AI (npm-metadata): Version 0.0.0 was the legitimate initial release of this 10+ year old package with 848k weekly downloads. Not a throwaway malicious package. ai
bogus-package bogus-package AI (bogus-package): Tiny payload and minimal README are consistent with a small, focused DOM utility library. Package is legitimate with high download counts and long history. ai

Versions (showing 5 of 5)

Version Deps Published
1.1.0 1 / 5
1.0.2 1 / 5
1.0.1 1 / 5
1.0.0 1 / 4
0.0.0 0 / 1

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.2

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.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.