emotality/laravel-everlytic

Project backingcaution

The registry namespace and repository owner match, but both represent a personal user account rather than an organization. This leaves the project with limited visible ownership depth.

Repo commit activitycaution

There were 0 commits and 0 active maintainers in the last three months. Recent releases provide some compensation, but the lack of observed development activity is a maintenance concern.

Repo toolingcaution

Composer build tooling is present, but no security-scanning tools were detected. For a small Laravel integration this is a hygiene gap, not evidence that the release is unsafe.

Security policycaution

The repository has no security policy. That reduces transparency about vulnerability reporting and response expectations, though it does not by itself indicate abandonment.

Workflow auditcaution

The single workflow was fully analyzed with no high-confidence audit findings or dangerous triggers, but both action references are unpinned. The workflow has no top-level permissions block, which is acceptable on its own.