denodeify

Release historydanger

The latest release was published over 11 years ago, with no releases in the last 12 months. This is the strongest maintenance concern, although the package has a stable 1.2.1 release history rather than repeated instability.

Repo commit activitydanger

The repository recorded 0 commits and 0 active maintainers over the last 3 months, and was last pushed in 2017. That indicates prolonged inactivity and raises abandonment risk.

Maintainerscaution

The package has one registry maintainer, which creates a thin operational base. The linked repository is owned by the same individual, so this is a real capacity limitation rather than an unexplained metadata gap.

Repo issue activitycaution

There were no new or closed issues or pull requests in the last month, with two open issues and one open pull request. This reinforces the evidence of inactive maintenance.