fijma/cobber

Its small, tested codebase, clear MIT licensing, and minimal dependency footprint make it easy to inspect. Maintenance appears to have stopped years ago, so adopting it creates substantial abandonment risk.

Latest v1.0.2

Packagist

43%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The package has only two releases, both from 2015, with no releases in the last 12 months. This strongly indicates the project is no longer actively maintained.

Repo commit activity

There were zero commits and zero active maintainers in the last three months. Combined with the 2015 release history, this is strong evidence of abandonment risk.

Project backing

The package and repository are owned by the same individual account, with no organization backing shown. That leaves a relatively thin visible support structure for an already inactive project.

Repo popularity

The repository has zero stars and forks and one watcher. Low adoption is supporting evidence of limited community backing, though it is not decisive by itself.

Repo tooling

Composer is used as the build tool, but no security scanning tools are present. The missing scanning is a modest hygiene gap, not a standalone adoption blocker.