denysloshkarev/laravel-api

Release historydanger

The package has only two releases, with the latest published over six years ago and none in the last 12 months. This indicates a largely inactive release history for a framework integration package.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers over the last three months. Combined with the old last push, this is strong evidence that maintenance has stopped.

Repository archiveddanger

The repository is not archived, but its last push was over six years ago, so the unarchived status does not offset the evidence of abandonment.

Dependency profilecaution

The package has only two runtime dependencies and no development dependencies, which is a small dependency surface, though the lack of development tooling gives little evidence of ongoing project validation.

Project backingcaution

The registry namespace and repository owner match, but the backing is an individual account rather than an organization. This is coherent ownership, though it offers limited redundancy for a single-maintainer project.