mikica/zf2-cookie

Release historydanger

The package has had no releases in nearly 11 years; its four releases were concentrated on the first day, with none in the last 12 months. This is strong evidence of abandonment risk.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers over the last three months, consistent with the release history and indicating that maintenance has stopped.

Project backingcaution

The repository is owned by an individual rather than an organization, so there is no demonstrated organizational backing to compensate for the single-person maintenance history.

Repo toolingcaution

Composer is used for the build, but no security scanning tools are configured. This is a hygiene and transparency weakness, though not evidence that the release is unsafe by itself.

Security policycaution

The repository has no security policy, leaving no documented process for reporting or handling vulnerabilities. For a dependency this old, that adds a meaningful transparency concern.