karmabunny/visor

This is a usable, transparently packaged PHP library with a stable major version, a matching and organization-backed repository, tests, a clear README, no install-time lifecycle scripts, no deprecation status, and recent registry releases. The main concerns are that repository commit activity is currently absent, issue and pull-request activity is stagnant, the repository has no security policy or security scanning, and its GitHub workflow does not declare top-level token permissions; these are meaningful hygiene and maintenance risks, although they do not indicate abandonment or make the release unfit by themselves.

Latest v2.3.6

Packagist

72%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Repo commit activity

The repository recorded 0 commits and 0 active maintainers during the last 3 months. This conflicts with the strong recent registry release history and raises a real concern about current source-level maintenance.

Repo issue activity

There are no open issues, but one pull request remains open and there were no new or closed issues or merged pull requests in the last month. This indicates limited visible collaboration and responsiveness.

Repo popularity

The repository has 0 stars, 1 fork, and 4 watchers. Low popularity is only supporting evidence and does not outweigh the package's release history and repository structure, but it provides little independent community validation.

Repo tooling

Composer build tooling is present, but no security scanning tools were detected. The absence of scanning is a security-process gap, though it is not by itself evidence that the package is unsafe.

Security policy

The repository has no security policy. For a small testing and local-server utility this is a transparency and vulnerability-reporting gap, but it is not a severe health failure on its own.