Package Health/davidpeach/composer-manuscript

davidpeach/composer-manuscript

Ten open issues, no security scanning, and only four unpinned workflow references weaken confidence in ongoing care. MIT licensing, a tested codebase, release notes, and a very small runtime dependency footprint provide useful transparency.

Latest 5.2.0

Packagist

55%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The package has 25 releases since 2021, but its latest release was over three years ago and there were no releases in the last 12 months, indicating stalled maintenance.

Repo commit activity

The repository recorded zero commits and zero active maintainers in the last three months, consistent with the long release gap and raising abandonment risk.

Repo issue activity

Ten issues remain open, with no issues or pull requests closed in the last month; this suggests unresolved maintenance demand, though only a short recent window is available.

Repo tooling

The project uses Composer, but no security scanning tools are configured, leaving a meaningful transparency and maintenance gap for dependency health.

Security policy

No repository security policy is present, reducing clarity about how vulnerabilities should be reported; this is a hygiene concern rather than evidence that the package is unsafe.