arachne/verifier

Release historydanger

The latest release was published on 27 July 2018, about 8 years before collection, with no releases in the preceding 12 months. That long release gap is strong evidence of abandonment risk for a dependency.

Repo commit activitydanger

The repository recorded no commits or active maintainers in the last 3 months, consistent with its last push being about 7 years ago. This substantially weakens confidence in ongoing maintenance.

Repo toolingcaution

Composer is used for builds, but no security scanning tools are reported. For an older package this leaves a modest assurance gap, without proving poor code quality.

Security policycaution

The repository has no published security policy. This is a transparency and vulnerability-reporting gap, although it does not by itself show that the package is unsafe.