psalm/psalm-plugin-api

Usable with caveats: it is a small, clearly backed API metapackage with a matching repository and no deprecation, but maintenance evidence is thin. Only two releases exist, the current line is still 0.x, and there has been no commit activity in the last three months.

Latest 0.2.0

Packagist

68%

Total Score

Maintainer Stability

Maturity

Supply Chain

Health Score Breakdown

Release history

Only two releases have been published over about six months, with roughly 179 days between them. That is limited maturity evidence for an API package, although the documented purpose suggests releases correspond to upstream API changes.

Repo commit activity

There were zero commits and zero active maintainers in the last three months. Although the repository was recently pushed and the package has only two files of substance, the lack of recent commit activity leaves maintenance capacity uncertain.

Repo issue activity

There are no open issues or pull requests and no issue or pull-request activity in the last month. This is neutral for a tiny API metapackage, but it provides little evidence of an active user or contributor community.

Repo popularity

The repository has zero stars, forks, and watchers, providing no popularity-based support for maturity. Popularity is only supporting evidence, so this modestly lowers confidence rather than making the package unfit.

Repo tooling

Composer is used as the build tool, fitting this PHP metapackage, but no security scanning tooling is configured. The absence is a transparency gap, though the repository contains no executable implementation.