jazzsequence/museum-core

A clear README, exact-version release notes, and a matching source repository improve transparency. The single maintainer, absent security policy, and no recent issues or commits leave little evidence of ongoing support.

Latest 2.1.7

Packagist

42%

Total Score

Maintainer Stability

Maturity

Supply Chain

Health Score Breakdown

Release history

The registry has only one release, published 615 days ago, with no releases in the last 12 months. This strongly limits evidence of ongoing maintenance.

Repo commit activity

The repository had zero commits and zero active maintainers in the last three months. Combined with the README's statement that the project is no longer actively maintained, this is strong abandonment evidence.

Maintainers

Only one registry maintainer is listed, leaving a thin publishing base. The repository is user-owned rather than organization-backed, so there is no shown backing to compensate for that concentration.

Repo issue activity

There were no new or closed issues and no pull-request activity in the last month, alongside five open issues, providing little evidence of active support.

Repo tooling

Composer is used as a build tool, which supports reproducible package handling, but no security scanning tools are configured. This is a modest transparency and maintenance gap rather than a standalone severe risk.