munusphp/munus

The MIT license, release notes, and repository tests provide useful transparency. The absent security policy and unpinned workflow actions leave operational safeguards weaker than mature projects.

Latest 0.17.0

Packagist

62%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Maintainers

Only one account has registry publishing access, which is a limited publishing bus. The organization-owned repository provides some backing, so this is a minor concern rather than a severe risk.

Release history

The package has 25 releases over about 6 years, but it has had no releases in the last 12 months and the latest release was about 21 months ago. This is meaningful evidence of slowed maintenance.

Repo commit activity

The repository recorded zero commits and zero active maintainers in the last 3 months. Combined with the absence of releases in the last year, this indicates currently inactive development.

Repo issue activity

There were no new or closed issues or pull requests in the last month, with two issues remaining open. This is a modest sign of low project activity rather than a severe abandonment indicator.

Repo tooling

Composer is used for the build, but no security scanning tool was detected. The missing scanning automation is a hygiene gap, not evidence that the release is unsafe by itself.