rajkumar14051988/mage

The MIT license and small dependency set make the package easy to inspect and adopt. Its generic README provides little integration guidance, while the lack of security tooling leaves maintenance risk unresolved.

Latest v3.0.2

Packagist

35%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The latest release was published in April 2018, with no releases in the last 12 months; this is strong evidence of abandonment for a dependency assessed today.

Repo commit activity

There were zero commits and zero active maintainers in the last three months, consistent with the release history and indicating a severe abandonment risk.

Package file tree

The package and repository each contain only three files—LICENSE.txt, README.md, and composer.json—indicating very limited project transparency and no visible implementation or test structure.

Package scaffolding

The artifact includes a README, and the absence of tests or a changelog is normal packaging practice; however, the README is generic GitHub Pages text rather than package documentation.

Project backing

The package and repository are owned by an individual user rather than an organization, so the thin ownership context offers no visible organizational maintenance capacity.