command-exists

Repo commit activitydanger

The repository had zero commits and zero active maintainers in the last three months. Combined with the old latest package release, this is the strongest evidence that ongoing maintenance is limited.

Build provenancecaution

No build attestation or trusted-publisher provenance is available. This limits publication transparency, but it is a supply-chain transparency gap rather than evidence that the package is unfit.

Maintainerscaution

Only one registry account has publish access. That is a limited publishing base for continuity, although registry access records do not establish who actively maintains the project.

Project backingcaution

The repository is owned by an individual user rather than an organization, so there is no visible organizational backing to provide maintainer redundancy.

Release historycaution

The package has 16 releases over roughly 12 years, but the latest release was in April 2020 and there were no releases in the last 12 months. The long period without a release lowers confidence in active maintenance, even for a stable utility.