mpstr24/laravel-api-responses

Project backingcaution

The repository and registry are owned by the same individual account, so the package has direct ownership alignment but no organizational backing indicated by the collected data. This leaves a relatively thin maintenance base.

Release historycaution

The package has only two releases, with none in the last 12 months and the latest release about one year ago. This suggests limited ongoing maintenance capacity.

Repo commit activitycaution

There were no commits and no active maintainers in the last three months, despite the repository being about one year past its latest push. This is a concrete sign that maintenance may have stopped.

Security policycaution

The repository has no security policy. For a small API helper this is not severe, but it reduces transparency about vulnerability reporting and maintenance response.

Workflow auditcaution

All eight analyzed action references are unpinned, which weakens workflow reproducibility, and the release workflow installs a package outside a lockfile. The audit found no high- or medium-confidence dangerous workflow behavior, so this is a hygiene caution rather than a severe risk.