pamkil/yii2-daemon

Release historydanger

The package has had no release in more than eight years and only four releases overall, which is strong evidence of abandonment for a dependency that may need compatibility fixes.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers in the last three months, consistent with the long release gap and leaving no recent maintenance capacity visible.

Maintainerscaution

Only one registry maintainer is listed, leaving a thin publishing base; the repository is user-owned rather than organization-backed, so there is no provided backing signal to offset that concentration.

Package file treecaution

The published and repository trees each contain only five files, suggesting a very small and minimally developed project; the compact scope may partly explain the size, but it provides little evidence of ongoing maturity.

Repo toolingcaution

Composer build tooling is present, but no security-scanning tools are configured. This is a hygiene gap that adds some transparency and maintenance risk, not an immediate dependency blocker.