Package Health/atomita/wordpress-eloquent

atomita/wordpress-eloquent

The package is small and easy to inspect, with a matching repository, MIT licensing, and a clear file layout. Its maintenance record is too stale for a dependable application dependency, and the project lacks tests and security-scanning evidence.

Latest v0.0.3

Packagist

38%

Total Score

Maintainer Stability

Maturity

Supply Chain

Health Score Breakdown

Release history

The latest release was about 8 years and 10 months ago, with no releases in the last 12 months and only three releases overall. This is strong evidence of abandonment risk for a library dependency.

Repo commit activity

The repository recorded zero commits and zero active maintainers in the last 3 months, consistent with the stale release history. No newer activity compensates for this maintenance gap.

Package scaffolding

The artifact includes a readable README, but it has no tests or changelog; absent tests and changelogs are normal packaging practice and are not themselves gaps. The short README provides only limited consumer guidance.

Repo popularity

The repository has zero stars and forks and one watcher. Popularity is only supporting evidence, but these very low figures provide no community-maintenance signal alongside the inactive repository.

Repo tooling

Composer is used as a build tool, which supports a conventional package structure, but no security-scanning tools are configured. The missing scanning is a modest transparency and hygiene concern.