mikealmond/color

Clear documentation, a matching source repository, a permissive license, and simple dependencies support adoption. Ongoing maintenance is uncertain because there have been no commits or releases since October 2021, and no security tooling or policy is present.

Latest v0.1.5

Packagist

62%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Project backing

The package and repository are owned by the same individual account, providing clear ownership but no organizational backing or maintainer redundancy.

Release history

The package has 10 releases but none in the last 12 months; its latest release was in October 2021. This long release gap lowers confidence in ongoing maintenance.

Repo commit activity

There were no commits and no active maintainers in the last three months. Combined with the old last push and release, this is the strongest evidence of possible abandonment.

Repo issue activity

There are no open issues or pull requests and no recent issue or pull-request activity. This is consistent with a quiet, possibly stable project, but it does not demonstrate active maintenance.

Repo tooling

Composer is used for builds, but no security scanning tool is detected. The missing scanning is a hygiene gap, though it does not outweigh the otherwise small and clear dependency profile.