znbundle/messenger

The MIT license, matching repository, and small runtime dependency set improve transparency. No tests or security scanning tools are evident, making future maintenance harder to verify.

Latest v0.0.2

Packagist

47%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

Only two releases were published, both in August 2020, with none in the last six years. This is strong evidence of abandonment risk despite the repository remaining available.

Repo commit activity

There were no commits and no active maintainers in the last three months. Combined with the old last push, this materially increases the risk that defects will remain unaddressed.

Repo popularity

The repository has zero stars and forks and only one watcher. Popularity is not decisive for a small package, but it provides little supporting evidence of community adoption or review.

Repo tooling

Composer build tooling is present, but no security scanning tool was detected. This is a maintenance and transparency gap rather than evidence of unsafe behavior on its own.

Security policy

The repository has no security policy. That weakens vulnerability-reporting transparency, though the absence is a secondary concern compared with the inactive release and commit history.