agile/phpeditdotenv

The four-file artifact is easy to inspect, and MIT licensing plus one runtime dependency reduce adoption friction. Repository ownership and package naming align, but there is little evidence of active project support.

Latest 1.0.1

Packagist

38%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

Only two releases were published, both in 2016, with no releases in the last 12 months. This is strong evidence of abandonment for a package a developer may need to maintain over time.

Repo commit activity

The repository recorded zero commits and zero active maintainers in the last three months, consistent with the last push being in 2016. No compensating activity signal is present.

Repo popularity

The repository has zero stars, zero watchers, and one fork. Popularity is not decisive by itself, but these very low figures provide no supporting evidence of a maintained user base.

Repo tooling

Composer is used for the build, but no security scanning tools are configured. This limits automated assurance for a package that reads and writes environment configuration.

Security policy

The repository has no security policy. This is a transparency and response-process gap, though it is less significant than the package's long-standing inactivity.