bee4/events

Registry deprecationdanger

Packagist marks the entire package as abandoned, with no replacement package identified. This is a severe adoption risk because future fixes and support are unlikely.

Release historydanger

The package has had no releases in the last 12 months, and its latest release is from June 2016. This strongly indicates abandonment despite its earlier release activity.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers in the last three months, consistent with the archived state and leaving no evidence of current maintenance capacity.

Repository archiveddanger

The linked repository is archived and was last pushed in June 2016, so the source is no longer actively maintained.

Security policycaution

The repository has no security policy. This adds a transparency gap, although the much larger concern is the project's apparent abandonment.