Package Health/experteam/api-laravel-crud

experteam/api-laravel-crud

This is a usable, established package with more than five years of release history, 55 releases, eight releases in the last 12 months, a stable non-prerelease version, a non-deprecated registry status, and a linked repository that matches the package and references it in its README. However, maintenance evidence is mixed: the repository was pushed recently and the latest release is current, but there were no commits or active maintainers in the preceding three months. The package also has no tests, changelog, security policy, or security-scanning tooling, and its repository has no CI workflows. These gaps do not make it unfit to use, but they reduce transparency and confidence in ongoing maintenance, so dependency adoption should include normal version pinning and review of updates.

Latest 3.7.5

Packagist

68%

Total Score

Maintainer Stability

Dependencies

Maturity

Supply Chain

Health Score Breakdown

Dependency profile

The package has four runtime dependencies, including Laravel and one related Experteam package, with no development dependencies. The runtime profile is not excessive, though the absence of dev dependencies also provides no evidence of packaged testing or development validation.

Package scaffolding

The package has a README and the repository uses GitHub Releases, but neither the artifact nor repository contains tests or a changelog. For a framework service package, the missing tests are a meaningful maintenance gap rather than merely a consumer-ergonomics issue.

Project backing

The repository is owned by the user account experteam-mx rather than an organization. This provides less formal backing evidence, but the matching repository and package mention establish a credible project relationship.

Repo commit activity

The repository recorded 0 commits and 0 active maintainers in the last three months. This conflicts with the recent push and current release history and creates a meaningful concern about ongoing source-level maintenance.

Repo issue activity

There are no open issues or pull requests and no issue or pull-request activity in the last month. This is neutral to mildly concerning: it shows no unresolved queue, but also no observed community or maintenance interaction.