p3k/caterpillar

Release historydanger

The latest release was in March 2017, with no releases in the last 12 months and only three releases overall. This is strong evidence of abandonment risk for a dependency, despite the package not being deprecated.

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 lowers confidence that defects or compatibility issues will be addressed.

Repo issue activitycaution

There was no issue or pull-request activity in the last month, and one issue remains open. This supports the conclusion that maintenance is currently inactive, although the short window is only corroborating evidence.

Repo toolingcaution

Composer build tooling is present, but no security scanning tools were detected. This is a modest repository hygiene gap rather than evidence that the release is unsafe by itself.

Security policycaution

The repository has no security policy, leaving no documented channel or process for reporting vulnerabilities. For an old, inactive package, that transparency gap is more consequential.