neo-async

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers in the last three months. Combined with the old latest release, this is the strongest concern for ongoing maintenance.

Build provenancecaution

No build attestation or trusted-publisher provenance is available, leaving publication origin less transparent than modern best practice.

Maintainerscaution

Only one registry account has publish access. That is a thin publishing base and increases continuity risk, although access records alone do not establish actual maintenance activity.

Project backingcaution

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

Release historycaution

The package has 77 releases and a long history, but it has had no release in nearly six years, which is a meaningful sign of inactivity for a dependency.