body

Release historydanger

The latest release was published in June 2015, with no releases in the last 12 months. This long release gap is a substantial maintenance concern, although the package had 21 releases and a rapid historical cadence.

Maintainerscaution

Only one registry account has publish access. The linked repository is user-owned rather than organization-backed, so the narrow publishing base provides limited resilience if that maintainer stops maintaining the package.

Project backingcaution

The repository is owned by an individual account, not an organization. That gives less visible institutional backing, consistent with the single registry maintainer.

Repo commit activitycaution

The repository had zero commits and zero active maintainers in the last three months. A push in February 2024 provides some compensating evidence, but current activity remains weak.

Repo toolingcaution

No build tool or security-scanning tool was detected. For a small JavaScript package this is not severe, but it leaves fewer automated safeguards around maintenance and releases.