richweber/yii2-phirehose

Release historydanger

The package has had only three releases, all effectively concentrated by 2015, with no release in over 11 years. This is strong evidence of abandonment for a dependency targeting an external API.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers in the last three months, consistent with the long release gap. The non-archived status does not compensate for the absence of current maintenance.

Repo popularitycaution

Three stars and two forks indicate a very small user and contributor footprint, offering little evidence of community support or resilience. This reinforces the maintenance concern but is not decisive alone.

Repo toolingcaution

Composer is used for the build, but no security-scanning tooling is present. That leaves dependency and repository issues less likely to be detected automatically.

Security policycaution

The repository has no security policy, which reduces transparency for reporting and handling issues. This is a secondary concern beside the much stronger abandonment evidence.