mosweed/mosweed_cms

Usable with caveats: the release is licensed, documented, non-deprecated, and backed by a matching repository, but maintenance appears stalled. There have been no registry releases in about 17 months and no repository commits in the last 3 months, with no security policy or automated security scanning.

Latest v1.1

Packagist

60%

Total Score

Maintainer Stability

Maturity

Supply Chain

Health Score Breakdown

Project backing

The registry namespace and repository owner match, but the repository is user-owned rather than organization-owned. This supports identity consistency while offering limited evidence of institutional backing.

Release history

Only three releases exist, and there have been no releases in the last 12 months; the latest release was about 17 months ago. This indicates a slow or stalled maintenance cycle for a package with a two-year history.

Repo commit activity

The repository recorded zero commits and zero active maintainers in the last 3 months. Combined with the old last push, this is a meaningful maintenance and abandonment concern.

Repo tooling

Composer build tooling is present, but no security scanning tools were detected. That weakens ongoing supply-chain hygiene, although it is not by itself evidence that the package is unsafe.

Repository archived

The linked repository is not archived, but its last push was about 17 months ago, so the unarchived status does not offset the evidence of inactivity.