affinity4/validate

Release historydanger

This package has only one release, published over four years ago, with no releases in the last 12 months. That is strong evidence of limited ongoing maintenance, though the included tests and release notes provide some maturity evidence.

Repo commit activitydanger

There were no commits and no active maintainers in the last three months. Combined with the repository's last push being over four years ago, this indicates little visible maintenance capacity.

Repo toolingcaution

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

Repository archivedcaution

The repository is not archived, but its last push was over four years ago. The active status is a positive counter-signal, while the long inactivity still supports the maintenance concern.

Security policycaution

The linked repository has no security policy. For a small library this is a limited governance gap, but it leaves vulnerability-reporting expectations undocumented.