Package Health/topotru/psalm-conditional-final

topotru/psalm-conditional-final

The repository has had no commits or active maintainers for about four months, and its two releases arrived within minutes of each other. Tests, documentation, licensing, and package ownership are otherwise clear, but workflow references are unpinned and no security policy is provided.

Latest 1.0.1

Packagist

58%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Repo commit activity

There were zero commits and zero active maintainers in the last three months, consistent with no repository push for about four months. For a newly released plugin, this is a meaningful abandonment risk.

Release history

The package is about 127 days old, but both releases were published within minutes on the same day and there have been no later releases. This indicates limited demonstrated maintenance rather than a mature release history.

Repo issue activity

There were no new or closed issues or pull requests in the last month, and none are currently open. This provides no evidence of ongoing maintenance or user support.

Repo popularity

The repository has zero stars, forks, and watchers. Low popularity is supporting evidence of limited adoption, but it is not decisive for a small package by itself.

Repo tooling

Composer is used as the build tool, but no security scanning tools are configured. The missing scanning is a modest repository hygiene gap rather than evidence that the package cannot be built.