tasoft/key-value-coding

Its small, dependency-light design and clear README make the code easy to inspect. With no recent maintenance or security policy, future compatibility and issue response are uncertain.

Latest 1.1

Packagist

42%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The package has made no release in more than 8 years, with zero releases in the last 12 months. This is strong evidence of abandonment for a library dependency.

Repo commit activity

The repository recorded zero commits and zero active maintainers in the last 3 months, consistent with the last release being more than 8 years ago. No provided signal shows renewed maintenance.

Project backing

The repository is owned by an individual user rather than an organization, and no separate project backing is shown. This leaves limited visible maintenance capacity alongside the inactivity evidence.

Repo popularity

The repository has zero stars, forks, and watchers, providing no evidence of an active user or contributor community. Popularity is supporting evidence, so this reinforces rather than determines the score.

Repo tooling

Composer is used for the build, but no security scanning tool is present. That is a modest hygiene gap, though the package's long inactivity is the larger concern.