bcrowe/growl

Release historydanger

The package has had no release in more than 10 years, despite 15 releases earlier in its history. That long gap is strong evidence of abandonment risk.

Repo commit activitydanger

There were zero commits and zero active maintainers in the last three months, consistent with the absence of releases since 2016 and indicating severe maintenance risk.

Project backingcaution

The package and repository are owned by the same individual account, so the source relationship is coherent, but there is no organizational backing shown to compensate for a single-owner project.

Repo toolingcaution

Composer build tooling is present, but no security scanning tools were detected. This is a minor transparency gap, secondary to the much larger maintenance concern.

Repository archivedcaution

The repository is not archived, which is a modest positive, but its last push was in March 2016 and does not show current maintenance.