Package Health/constant-null/eloquent-changed-by-user

constant-null/eloquent-changed-by-user

Its narrow scope and documented setup reduce adoption friction. Maintenance evidence is weak: there have been no releases or commits for about 10 years, with no tests or security scanning to support continued reliability. The declared MIT license and lack of install scripts are positive.

Latest v0.1.1

Packagist

38%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The package has had only two releases, both on the same day in December 2015, and none in roughly 10 years. This is strong evidence of abandonment for a dependency that may need compatibility updates.

Repo commit activity

The repository recorded zero commits and zero active maintainers in the last three months, consistent with the last push being about 10 years ago. No newer activity compensates for this gap.

Repo popularity

The repository has one star and no forks, providing little supporting evidence of community review or shared maintenance. Popularity is only supporting evidence, but it reinforces the lack of activity.

Repo tooling

Composer is used for the build, but no security-scanning tools are configured. That leaves an additional verification gap in an otherwise very small project.

Repository archived

The repository is not archived, which avoids an explicit abandonment marker, but its last push was about 10 years ago. The unarchived status does not compensate for the prolonged inactivity.