jedrzej/withable

A clear MIT license, README, tests, and a small runtime dependency set make the package straightforward to evaluate and integrate. There is no repository security policy or automated security scanning.

Latest 0.0.6

Packagist

58%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The package has had 6 releases since August 2015, but none in the last 12 months; the latest release was in September 2019. This long release gap is meaningful abandonment risk for a dependency.

Repo commit activity

The repository recorded 0 commits and 0 active maintainers in the last 3 months. Combined with no registry releases in the last year, this materially raises abandonment risk.

Project backing

The repository is owned by an individual account rather than an organization. This does not establish a problem by itself, but it provides less visible backing for a package whose recent maintenance is inactive.

Repo issue activity

There are 3 open issues and 1 open pull request, but no issues or pull requests were opened or closed in the last month. This supports the broader picture of inactive maintenance.

Repo tooling

Composer build tooling is present, but no security scanning tools were detected. That is a transparency and maintenance gap, though not evidence that the package is unsafe.