enolaphp/api-rest-client

The MIT license, minimal dependency surface, and absence of install scripts reduce operational friction. The repository also lacks a security policy and security scanning, leaving maintenance and response practices unclear.

Latest v1.0

Packagist

30%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The package has had only one release, published about eight years ago, with no releases in the last 12 months. This is strong evidence of abandonment for a dependency expected to receive maintenance.

Repo commit activity

The repository recorded zero commits and zero active maintainers during the last three months, consistent with the long release gap and leaving little evidence of ongoing maintenance.

Repo package mention

The linked repository name does not match the package name, and its README does not mention the package. That makes the source relationship difficult to verify and raises provenance concerns.

Repo popularity

The repository has zero stars and forks and only one watcher. Popularity is supporting evidence rather than a verdict, but these figures provide no additional community or continuity signal.

Repo tooling

Composer is used for the build, but no security scanning tools are configured. This leaves dependency and code security checks less transparent.