m1/env

Documentation is strong, the repository contains tests and release notes, and the package has no install scripts or deprecation notice. Its single maintainer and absent security scanning leave less assurance for long-term support.

Latest 2.2.0

Packagist

61%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Maintainers

One registry publishing account is listed. That is a modest continuity risk for an independently owned package, though it does not by itself show abandonment.

Release history

The latest registry release was published more than six years ago, with no releases in the last 12 months. The package has a long history and ten releases, but its current maintenance appears inactive.

Repo commit activity

The repository recorded no commits and no active maintainers in the last three months, consistent with a project that has seen little recent development. Its last push was more than four years ago, which limits confidence in ongoing support.

Repo issue activity

There were no new or closed issues or pull requests in the last month, despite four open issues and one open pull request. This suggests limited current project responsiveness.

Repo tooling

Composer is used for the build, but no security-scanning tool was detected. The build setup supports reproducibility, while the missing scanning reduces maintenance assurance.