401clicks/laravel-logger

Release historycaution

All three releases arrived within roughly seven hours on the first release day, and there have been no later releases over the package's roughly eight-month lifetime. This is limited evidence of sustained maintenance.

Repo commit activitycaution

There were zero commits and zero active maintainers in the last three months. Combined with the one-day release burst, this is the strongest evidence that ongoing maintenance is unproven.

Repo popularitycaution

The repository has one star, no forks, and no watchers, so there is little community evidence to supplement the thin maintenance record. Low popularity alone is not a rejection reason.

Repo toolingcaution

Composer is used for the build, but the repository reports no security scanning tools. This is a maintenance and transparency gap, though not a severe risk by itself.

Security policycaution

The repository has no security policy, leaving no documented process for reporting or handling vulnerabilities. This lowers project transparency for a package that sends application logs to an external service.