glaivepro/cachepage

Release historydanger

The latest registry release was about five years ago, with no releases in the last 12 months. This is strong evidence of slowing maintenance, although the package has an established release history.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers in the last three months, consistent with the long release gap. This materially increases abandonment risk.

Maintainerscaution

Only one account has registry publish access, which limits publishing resilience. The organization-backed repository provides some compensation, so this is a caution rather than a severe standalone risk.

Repo toolingcaution

Composer is used as the build tool, but no security-scanning tool was detected. The absence of automated security checks is a modest hygiene gap.

Security policycaution

The repository has no security policy, leaving vulnerability reporting and response expectations undocumented. This is a transparency and maintenance gap, though it does not by itself make the package unfit.