w7/rangine-command

Release historydanger

The package has 47 releases and a historically regular median interval of about 11 days, but it has had no release in roughly four years and none in the last 12 months. The long period without a release materially raises abandonment risk.

Repo commit activitydanger

The repository recorded no commits and no active maintainers in the last three months. Combined with the last push being about three years ago, this is strong evidence that maintenance has stalled.

Repo package mentioncaution

The repository name does not exactly match the package name, and no README mention was available. This leaves some uncertainty about package-to-repository ownership, though the repository naming is consistent with a package subproject.

Security policycaution

The repository has no security policy. This is a transparency and maintenance gap, although it is less decisive than the absence of recent release and commit activity.

Version stabilitycaution

The assessed version is v3.0.1, while the registry reports v2.1.8 as the latest version. Although the versions are marked stable and not prereleases, this mismatch weakens confidence in release metadata and version tracking.