Package Health/experteam/api-laravel-base

experteam/api-laravel-base

Usable with caveats: it has a stable release history, a matching source repository, and a recent release, but maintenance evidence is thin. Zero commits in the last three months, no tests or security policy, and a very small maintainer and user base increase the risk of slow support.

Latest 2.3.1

Packagist

67%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Maintainers

Only one registry account has publish access. A single publisher is not itself proof of poor maintenance, but combined with zero recent commits it increases the risk that support depends on one person.

Project backing

The registry namespace and repository owner correspond to the same project identity, but the repository owner is a user rather than an organization. This supports basic ownership consistency while leaving a relatively small backing structure.

Repo commit activity

There were no commits and no active maintainers in the last three months. Although the package had a release about 8 months ago, the lack of recent repository work raises maintenance and abandonment concerns.

Repo popularity

The repository has zero stars and forks and only two watchers. Popularity is not required for a small package, but these counters provide little independent evidence of broad review or community support.

Repo tooling

Composer is used as the build tool, which fits the package ecosystem, but no security scanning tools are configured. This leaves a modest transparency and detection gap.