zenlix/zenenv

The package is very small and easy to inspect, with one runtime dependency, a matching MIT license, and clear usage documentation. Its source has seen no release or push activity for about 10 years, with no tests or security policy, so maintenance support is effectively absent.

Latest 1.4

Packagist

38%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The package has only 3 releases, all concentrated in July 2016, and none in the last 12 months; the latest release is about 10 years old. This is strong evidence of abandonment for a dependency that may need compatibility fixes.

Repo issue activity

There are no open issues or pull requests and no recent activity. For this tiny package that is not inherently bad, but together with the old release date it provides no evidence of ongoing maintenance.

Repo tooling

The repository uses Composer for builds, but has no security-scanning tools. The straightforward project structure makes this a modest hygiene gap rather than a severe risk.

Repository archived

The repository is not archived, which avoids an explicit abandonment marker, but its last push was about 10 years ago and does not offset the stale release history.

Security policy

The repository has no security policy. This is a transparency gap, especially for a package that edits environment files, although the small codebase limits the impact compared with a larger dependency.