imedge/web-select2

The project has a clear MIT license, tests, organization backing, and only one runtime dependency. Its release cadence is slow, recent commit activity is absent, and all six workflow actions are unpinned; no security policy is published.

Latest v0.6.0

Packagist

65%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

Only two releases span about 23 months, with one release in the last 12 months and a median interval of about 18 months. This indicates a slow maintenance cadence, though the package was released recently enough that abandonment is not established.

Repo commit activity

There were zero commits and zero active maintainers during the last three months. Combined with the long release interval, this leaves current maintenance capacity uncertain.

Repo tooling

Composer build tooling is present, but no security-scanning tools were detected. The build setup is established, while security automation remains a transparency gap.

Security policy

The repository has no published security policy. This weakens vulnerability-reporting transparency, although it is not by itself evidence that the package is unsafe.

Version stability

Version v0.6.0 is not a stable major release, which suggests the public API may still change. It is not marked as a prerelease, so this is a moderate rather than severe concern.