bisweb/deployer

It has a clear GPL-3.0 license, a usable README, and an organization-backed repository. The missing security policy and minimal repository activity leave support and maintenance capacity uncertain.

Latest v1.1.0

Packagist

58%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

Only two releases were published, both about 14 months ago, with no releases in the last 12 months. This is a meaningful maintenance concern for a package developers may need to keep compatible.

Repo commit activity

The repository had no commits and no active maintainers in the last 3 months. Combined with no releases in the last 12 months, this raises abandonment risk.

Repo issue activity

There were no new or closed issues or pull requests in the last month and no open work items. This does not prove abandonment, but it provides no evidence of active support.

Repo popularity

The repository has zero stars, forks, and watchers. Popularity is only supporting evidence, but these counts provide no external sign of adoption or community support.

Repo tooling

Composer is used as the build tool, which fits the package ecosystem, but no security scanning tools are present. The missing scanning is a modest hygiene concern rather than a health verdict.