yesccx/laravel-log-viewer

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers in the last three months, while its last push was about nine months ago. That is the strongest evidence of slowing or absent maintenance.

Maintainerscaution

One registry publishing account is listed. Because the repository is user-owned rather than organization-owned, this provides little evidence of maintenance capacity and adds some resilience concern.

Project backingcaution

The registry namespace and repository are owned by the same individual account, with no organization backing shown. This is consistent ownership but offers limited evidence of broader project support.

Release historycaution

The package is young, with three releases over about one week and no later releases in the observed period. This shows an initial release burst but not an established maintenance record.

Repo toolingcaution

Composer build tooling is present, but no security scanning tools were detected. The missing scanning is a modest transparency and maintenance gap, not evidence that the package is unsafe.