Package Health/classicpress-plugins/classicpress-seo

classicpress-plugins/classicpress-seo

Tests, release notes, a clear license, and organization backing provide useful maintenance context. More than two years without a release or recent commits, no security policy, and unpinned workflow actions increase maintenance and build-transparency risk.

Latest v2.3.0

Packagist

58%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Repo commit activity

There were no commits and no active maintainers in the last three months. Combined with no registry releases in over two years, this is strong evidence of slowed maintenance.

Release history

The package has 35 releases since 2021, but none in the last 12 months and its latest release was over two years ago. This indicates a substantial maintenance slowdown despite the established release history.

Repo issue activity

There are 20 open issues and two open pull requests, but no new or closed issues or merged pull requests in the last month. The unresolved queue adds a modest maintenance concern alongside the inactive release history.

Repo tooling

Composer is used as a build tool, supporting reproducible project structure, but no security scanning tools were detected. The missing scanning layer is a modest transparency gap.

Security policy

The repository has no security policy file, leaving reporting and response expectations undocumented for a security-sensitive SEO plugin.