coco-project/tree

Tests, licensing, and a small dependency set support straightforward use. The project has been inactive for about two years and lacks security policy or scanning, so future maintenance and vulnerability response are uncertain.

Latest v1.0.15

Packagist

58%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The package has 15 releases, but none in the last 12 months; its latest release was about two years ago. This indicates a meaningful maintenance slowdown despite a previously established release history.

Repo commit activity

The repository recorded no commits and no active maintainers in the last three months, consistent with the long release gap. That weakens confidence that bugs or compatibility issues will be addressed promptly.

Repo popularity

The repository has 0 stars and 0 forks, with 1 watcher. Popularity is not decisive, but this provides little supporting evidence of broad adoption or external review.

Repo tooling

Composer build tooling is present, but no security scanning tools were detected. The build setup is established, while automated security coverage is limited.

Security policy

The repository has no security policy, leaving no documented process for reporting or handling vulnerabilities. This is a transparency and response-readiness gap.