brick/event

Registry deprecationdanger

Packagist marks the entire package as abandoned, with no replacement supplied; this is a direct warning against taking a new dependency on it.

Release historydanger

Only two releases exist, with the latest published in December 2019 and no releases in the last 12 months, indicating prolonged release inactivity.

Repo commit activitydanger

There were zero commits and zero active maintainers in the last three months, providing no evidence of ongoing maintenance capacity.

Repository archiveddanger

The linked repository is archived, which is a severe abandonment signal even though it was pushed in May 2024.

Repo issue activitycaution

There are no open issues or pull requests and no recent activity, which is consistent with a dormant project rather than active maintenance.