app-dev-panel/mcp-server

Usable with caveats: the package is backed by an organization, includes tests, and has a clean dependency and install profile. However, it has no package README and no commits from any maintainer in the last three months, so ongoing support is uncertain.

Latest v0.4

Packagist

55%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Package scaffolding

The artifact includes tests and the repository also contains a substantial unit-test suite, which supports basic project maturity. The missing README is a real usability gap for a package developers must integrate, while the missing changelog is not concerning because changelogs belong in the source repository and are not required in published artifacts.

Release history

Six releases in about 170 days, with a median interval of roughly 2 days, shows active early development and a usable release history. The short history also leaves limited evidence of long-term maintenance.

Repo commit activity

The repository recorded zero commits and zero active maintainers in the last three months, which is the clearest concern about current maintenance capacity. The recent release history and organization backing provide some context but do not show ongoing work after the initial development period.

Repo popularity

The repository has only 1 star and no forks or watchers, indicating limited external adoption. Popularity is supporting evidence rather than a decisive health measure, especially for a new organization-backed package.

Repo tooling

Composer is used for the build, but no security scanning tools were detected. The absence of scanning lowers transparency somewhat, although no workflow-based risk was observed.