20tries/arr

Release historydanger

The package has had only four releases, and none in the last nine years; its latest release was in March 2017. This is strong evidence of abandonment for a dependency that may need maintenance.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers in the last three months, consistent with the long release gap. The stable 1.0.1 version provides some maturity but does not offset the absence of current activity.

Repo popularitycaution

The repository has zero stars, forks, and watchers, providing no supporting evidence of community adoption or external maintenance. Low popularity alone is not decisive, but it reinforces the abandonment concern.

Repository archivedcaution

The linked repository is not archived, so it remains technically available for maintenance. Its last push in March 2017 still indicates that availability should not be confused with active upkeep.

Security policycaution

The repository has no security policy, reducing transparency about how vulnerabilities should be reported. This is a secondary hygiene gap rather than a standalone reason to reject the package.