pmvc-plugin/swagger

The package has a clear README, an MIT declaration, and a repository that matches its package name. Its small dependency surface and lack of install-time scripts reduce integration risk, but maintenance evidence is too weak for a dependable long-term choice.

Latest 0.1.9

Packagist

38%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

This package has only one release, published over 10 years ago, with no releases in the last 12 months. That is strong evidence of abandonment risk despite the absence of registry deprecation.

Repo commit activity

The repository has recorded no commits and no active maintainers in the last 3 months, consistent with the package's long period without releases. This materially weakens confidence in ongoing maintenance.

Repo popularity

The repository has no stars or forks and only one watcher. Popularity is supporting evidence rather than a verdict, but these counts provide no meaningful adoption signal to offset the maintenance concerns.

Repo tooling

Composer is used as the build tool, showing basic project tooling, but no security scanning tools are present. The missing scanning is a hygiene gap rather than evidence that the package is unsafe.

Security policy

The repository has no security policy. This reduces transparency for reporting and handling issues, though it is secondary to the much stronger abandonment signal.