djokicpn/laravel-email-audit-log

Maintainerscaution

Only one registry account can publish releases. That is a thin publishing base for a user-owned project and increases continuity risk, with no organizational backing shown to compensate.

Release historycaution

The latest release was over two years ago, with no releases in the last 12 months. This is a meaningful maintenance concern, although the package has nine releases and is not marked deprecated.

Repo commit activitycaution

The repository recorded zero commits and zero active maintainers in the last three months, consistent with the long release gap. The repository is not archived, but current maintenance capacity is not demonstrated.

Repo toolingcaution

Composer build tooling is present, but no security scanning tools are configured. The missing scanning reduces automated oversight, though it is not by itself a severe dependency risk.

Security policycaution

The repository has no security policy, so users have no documented channel or process for reporting security issues. This is a transparency and maintenance gap, not evidence of malicious behavior.