when

Release historydanger

The package has 63 releases and a historically regular cadence, but its latest release was about 9 years ago and there were no releases in the last 12 months. That strongly raises abandonment and compatibility risk despite its mature history.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers in the last 3 months. Combined with the last package release being about 9 years ago, this is strong evidence of stalled maintenance.

Build provenancecaution

No build attestation or trusted-publisher provenance is present, leaving publication origin less independently verifiable. This is a transparency gap, not evidence that the release is unsafe.

Lifecycle scriptscaution

A prepublish lifecycle script adds some install or publication complexity, though this is less concerning than install-time scripts that execute for consumers.

Repo issue activitycaution

There are 59 open issues and 8 open pull requests, with no issues or pull requests opened or closed in the last month. The backlog and lack of recent handling weaken maintenance confidence.