Package Health/wizardloop/broadcastmanager

wizardloop/broadcastmanager

The project has a clear license, release notes, and a published security policy. Repository commits have stopped for three months, and the only maintainer plus unpinned CI actions add ongoing maintenance and build-integrity concerns.

Latest 3.2.2

Packagist

66%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

100

Health Score Breakdown

Maintainers

Only one registry account has publishing access. That is a real continuity weakness for a user-owned project because there is no provided evidence of a broader publishing team.

Project backing

The registry and repository are owned by the same individual account, so ownership is consistent, but the provided evidence does not show organization backing.

Repo commit activity

The repository recorded zero commits and zero active maintainers in the last three months. This is the strongest maintenance concern, though it is partly offset by the release published at the start of that period.

Repo tooling

Composer build tooling is present, but no security scanning tools were detected. This is a modest transparency and maintenance gap rather than evidence of an unsafe release.

Workflow audit

The sole workflow was fully analyzed with no trigger or audit findings, but both of its action references are unpinned. That leaves CI exposed to changes in referenced actions and is a concrete build-reproducibility weakness.