beebmx/pipeline

Clear documentation, tests, licensing, and a minimal dependency set support straightforward adoption. The project has only one release and no recorded commits in the last three months, while its workflow uses two unpinned actions.

Latest 1.0.0

Packagist

60%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Project backing

The package and repository are owned by the same individual account, providing consistent ownership context but no organizational backing to offset the thin maintenance record.

Release history

The package has had only one release, published 821 days ago, with no releases in the last 12 months; this is substantial evidence of limited ongoing maintenance.

Repo commit activity

There were zero commits and zero active maintainers in the last three months, which weakens evidence of current maintenance capacity.

Repo popularity

The repository has one star and no forks, offering little community corroboration; this is supporting caution rather than a verdict by itself.

Repo tooling

Composer build tooling is present, but no security scanning tools were detected; this is a modest transparency and hygiene gap.