sergiors/pipeline

A clear README, tests, stable 2.0.0 release, and minimal runtime dependencies make integration straightforward. The project has not released or committed changes since April 2017, and it lacks security scanning and a security policy.

Latest 2.0.0

Packagist

42%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The package has only two releases, with the latest on April 19, 2017 and none in the last 12 months. This is strong evidence of prolonged inactivity, although the stable 2.0.0 release reduces version-churn risk.

Repo commit activity

There were zero commits and zero active maintainers in the last three months. Given the repository's last push in 2017, this indicates a long-standing lack of active maintenance.

Project backing

The package and repository are owned by the same individual account. This is consistent ownership, but it does not provide organizational backing to compensate for the inactive maintenance record.

Repo issue activity

There are no open issues or pull requests and no recent issue or pull-request activity. This is compatible with a small stable project, but it provides no evidence of current maintenance.

Repo tooling

The repository uses Composer and Phing for build tasks, which shows basic project tooling, but no security scanning tools are present.