sixlive/dotenv-editor

The MIT license, small dependency footprint, and clear documentation make adoption straightforward. The repository is intact and tested, but maintenance visibility is limited and workflow pinning is weak.

Latest v2.1.0

Packagist

64%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Project backing

The registry namespace and repository owner match, but the owner is an individual rather than an organization. This indicates a small maintainer setup without organizational backing.

Release history

The package has existed for about eight years and has seven releases, but it has had no release in the past 12 months. This lowers confidence in ongoing maintenance.

Repo commit activity

The repository recorded zero commits and zero active maintainers in the past three months. Combined with the lack of recent releases, this raises maintenance and abandonment concerns.

Repo issue activity

There has been no new or closed issue or pull request activity in the past month, with one open issue and one open pull request. This is a modest sign of limited current engagement.

Repo tooling

Composer is used for the build, but no security scanning tools were detected. The missing scanning is a hygiene gap rather than evidence of unsafe code.