bigsinoos/j-eloquent

The package has a clear README, a matching three-file source tree, and no install-time scripts. Its registry and repository activity have been inactive for years, while the project has no security policy or automated security scanning.

Latest 2.2.5

Packagist

43%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The latest release was published in February 2017, with no releases in the last 12 months; this is a substantial abandonment concern despite the package having ten releases overall.

Repo commit activity

There were zero commits and zero active maintainers in the last three months, consistent with a repository whose last push was in 2021; this materially increases maintenance and abandonment risk.

Project backing

The repository is owned by an individual user rather than an organization, and the registry namespace differs from the repository owner. This is consistent with the linked project but provides limited backing capacity.

Repo tooling

Composer is used for builds, but no security scanning tools are configured. The missing scanning is a hygiene gap rather than evidence that the package is unsafe.

Security policy

The repository has no security policy, reducing transparency for reporting and handling vulnerabilities in a package that has not been maintained recently.