cupoftea/prioritize-routes

Release historydanger

The package has had no release in nearly 10 years: its latest release was published on December 20, 2016, with only two releases total. This is strong evidence of abandonment despite the stable version.

Repo commit activitydanger

There were no commits and no active maintainers in the last three months, consistent with the nearly decade-long release gap. This materially increases abandonment risk.

Repo toolingcaution

Composer build tooling is present, but no security scanning tools were detected. That is a moderate transparency and maintenance gap, though it is less serious than the absence of recent development.

Repository archivedcaution

The linked repository is not archived, so it remains available for inspection. Its last push in January 2017 still indicates that availability is not the same as active maintenance.

Security policycaution

The repository has no security policy. For a small, inactive package this leaves vulnerability-reporting expectations unclear and provides little evidence of ongoing security maintenance.