emitter-component

Registry deprecationdanger

npm marks the package deprecated at package scope and explicitly directs consumers to the renamed component-emitter package. This is a decisive adoption risk even though the release itself is stable.

Release historycaution

The package has had no registry release in nearly three years, despite a long history and 12 total releases. That supports the deprecation concern and indicates no ongoing release maintenance.

Repo commit activitycaution

The repository recorded zero commits and zero active maintainers in the last three months, with its last push in December 2023. This indicates dormant maintenance rather than active support.

Repo package mentioncaution

The linked repository name does not match emitter-component and its README does not mention the package. Although this can occur with renamed or sub-package repositories, the ownership relationship is less transparent.

Workflow auditcaution

The single workflow was fully analyzed with no reported findings or untrusted triggers, but both of its two action references are unpinned. That leaves avoidable workflow reproducibility and supply-chain hygiene risk.