npm-conf

Release historydanger

The latest release was published in October 2017, with no releases in the last 12 months. This is a substantial maintenance concern even though the package has five releases and previously had roughly monthly releases.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers in the last three months. Combined with the lack of recent registry releases, this points to materially reduced maintenance activity.

Lifecycle scriptscaution

A prepublish lifecycle script is present. This adds build and publication behavior that consumers should understand, but the signal alone does not show malicious or unsafe execution.

Project backingcaution

The repository is owned by an individual account rather than an organization, so there is no demonstrated organizational backing to offset the narrow maintainer base.

Repo issue activitycaution

There are open issues and pull requests, but none were opened or closed in the last month. This indicates limited current project interaction without proving abandonment by itself.