event-target-polyfill

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers in the last three months, matching the long release gap and materially increasing abandonment risk.

Build provenancecaution

No build attestation or trusted-publisher metadata is available. This weakens publication transparency, though it is not by itself evidence that the package is unsafe.

Maintainerscaution

One registry maintainer is a thin publishing base. Individual ownership explains this structure, but it still provides limited redundancy if the maintainer becomes unavailable.

Project backingcaution

The repository is owned by an individual rather than an organization, so the single registry maintainer is consistent with the project’s backing but leaves limited visible succession capacity.

Release historycaution

The package has only four releases and none in the last two years and ten months, indicating a long period without published maintenance. Its small scope may partly explain the low cadence, but the gap still raises abandonment risk.