najibismail/laravel-exception-catcher

Maintainerscaution

One registry maintainer is reasonable for an individually owned package, but it leaves the project dependent on a single publisher and provides little redundancy if maintenance stops.

Release historycaution

The package has had no release in about a year, after nine releases concentrated in its first few weeks. That pause raises maintenance risk, though the release history shows the project was initially active.

Repo commit activitycaution

The repository recorded zero commits and zero active maintainers in the last three months, consistent with the roughly year-long release pause and suggesting limited ongoing maintenance.

Repo toolingcaution

Composer build tooling is present, but no security scanning tools were detected. That weakens the project's automated security hygiene without making the release unsafe by itself.

Security policycaution

The linked repository has no security policy. This is a transparency and issue-reporting gap, particularly for a package that handles exception details and sends them by email.