adrianbaez/data-manager

The MIT license, included tests, and focused dependency set make the package straightforward to inspect and integrate. Its minimal README and absent security policy leave limited guidance for long-term maintenance.

Latest 0.0.1

Packagist

40%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The package has only one release, published about eight years ago, with no releases in the last 12 months. This is strong evidence of an unmaintained project and outweighs the otherwise small scope.

Repo commit activity

The repository has had no commits and no active maintainers in the last three months, consistent with the last push being about eight years ago. This materially raises abandonment risk.

Package scaffolding

The package includes tests and a README, and the repository uses GitHub releases, providing some evidence of initial engineering discipline. The README is only 15 characters and there is no changelog, limiting consumer guidance.

Repo tooling

Composer is used as a build tool, which fits the package ecosystem, but no security scanning tooling is present. The tooling evidence is limited and does not offset the maintenance concerns.

Security policy

No security policy was found in the repository. This is a transparency gap, especially for a dependency that appears no longer to receive active maintenance.