illuminate/exception

Release historydanger

The latest release was published in December 2014, nearly 12 years before collection, with no releases in the last 12 months. That strongly indicates the release line is abandoned despite its earlier 58-release history.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers in the last three months, consistent with the long gap since the latest release and indicating no observed maintenance capacity.

Repository archiveddanger

The repository is not formally archived, but its last push was in April 2015. The non-archived status does not compensate for more than 11 years without observed repository updates.

Repo toolingcaution

Composer is used for the build, but no security scanning tools were detected. The missing scanning reduces maintenance hygiene without independently showing that the package is unsafe.

Security policycaution

The linked repository has no security policy, leaving vulnerability reporting expectations undocumented. This is a transparency gap, though less important than the prolonged inactivity.