cebe/yii2-lifecycle-behavior

Maintainerscaution

One registry account has publish access, and the project is backed by an individual repository owner rather than an organization. That is not inherently unsafe, but it leaves limited visible maintenance capacity alongside the inactive repository.

Release historycaution

The latest release was published in December 2018, with no releases in the last 12 months and only two releases overall. This is substantial evidence of stagnation for a dependency, despite the package being mature and stable.

Repo commit activitycaution

The repository recorded zero commits and zero active maintainers during the last three months, consistent with the long release gap. The repository is not archived, but there is no recent development evidence.

Repo toolingcaution

The project uses Make and Composer, showing basic build tooling, but no security scanning tools were detected. This modestly reduces confidence in ongoing maintenance hygiene.

Security policycaution

The repository has no security policy, leaving no documented process for reporting or handling vulnerabilities. This is a transparency gap, though it is less serious than abandonment or deprecation.