pendalff/eloquent-joins

Clear licensing, a focused file tree, and no install-time scripts reduce adoption friction. The repository is not archived, but its small footprint and limited project support leave compatibility uncertain.

Latest 0.0.1

Packagist

38%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The package has only one release, published about 10 years ago, with no releases in the last 12 months. That is strong evidence of abandonment for a library consumers may need to keep compatible with current Laravel versions.

Repo commit activity

The repository recorded 0 commits and 0 active maintainers in the last 3 months, consistent with the one-release history and indicating no current maintenance capacity.

Project backing

The package and repository are owned by the same individual account, with no organization backing shown. This is not inherently unhealthy, but it provides limited evidence of sustained maintenance capacity.

Repo popularity

The repository has 1 star, 0 forks, and 1 watcher, providing little evidence of a broad user or maintainer community. Popularity is supporting evidence, so this reinforces rather than determines the maintenance concern.

Repo tooling

Composer is used as a build tool, but no security-scanning tooling is present. The missing scanner is a modest transparency and hygiene gap, not a standalone adoption blocker.