lockfile

Release historydanger

The package has had no releases in the last 12 months, and its latest release was in April 2018. That long release gap materially increases abandonment and compatibility risk.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers in the last three months, consistent with the package being inactive. No provided signal shows current development that compensates for this.

Repository archiveddanger

The linked repository is archived, a strong sign that active maintenance and future fixes are unlikely. Its organization ownership provides context but does not offset the archived status.

Project backingcaution

The repository is owned by the npm organization, which indicates identifiable project backing. The repository’s archived state still shows that this backing is not currently providing active maintenance.

Repo issue activitycaution

There were no new or closed issues or pull requests in the last month, while open work remains. This suggests unresolved maintenance needs rather than active project stewardship.