Package Health/meiguonet/meiguonet-mgboot-dal

meiguonet/meiguonet-mgboot-dal

Clear licensing, package-to-repository alignment, and a small dependency surface help reduce adoption friction. The lack of tests and security scanning leaves limited evidence that changes would be caught or reviewed.

Latest 1.1.9

Packagist

42%

Total Score

Maintainer Stability

Maturity

Supply Chain

Health Score Breakdown

Release history

The package is over five years old, with 20 releases but none in the last five years and no releases in the past 12 months. That prolonged release silence is a substantial abandonment concern.

Repo commit activity

The repository recorded zero commits and zero active maintainers in the last three months, consistent with the long period since the latest release. This leaves little evidence of current maintenance capacity.

Repo popularity

The repository has zero stars and forks and only one watcher. Popularity is not required for a healthy package, but these counters provide no supporting evidence of broad review or community involvement.

Repo tooling

Composer is used for builds, but no security scanning tools are configured. For a data-access library, that weakens ongoing quality and dependency-risk monitoring.

Security policy

The repository has no security policy, so there is no documented path for reporting or handling vulnerabilities. This is a transparency gap, though it is not evidence of a vulnerability by itself.