arachne/parameter-validation

Release historydanger

The latest release was published in December 2017, with no releases in the last 12 months. This long release gap is strong evidence of abandonment risk for a dependency.

Repo commit activitydanger

There were no commits and no active maintainers in the last three months, reinforcing the long gap since the last release and indicating weak current maintenance.

Repo issue activitycaution

One issue and one pull request remain open, with no new or closed activity in the last month. This is a modest sign of limited project attention, though not conclusive alone.

Repo toolingcaution

Composer build tooling is present, but no security scanning tools were detected. That is a transparency and maintenance-hygiene gap, not evidence that the package is unsafe.

Security policycaution

The repository has no security policy, leaving vulnerability-reporting expectations undocumented. This is a modest transparency gap alongside the broader maintenance concerns.