Package Health/mjcodebase/net-mqtt-client-react

mjcodebase/net-mqtt-client-react

The dependency surface is modest and installation has no lifecycle scripts. MIT licensing, stable versioning, and release notes help transparency, but the tiny project provides limited evidence of sustained maintenance.

Latest 1.2

Packagist

55%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Package file tree

The complete package contains only 3 files, including two source files and composer.json. That may fit a narrow adapter, but it leaves little visible project structure for testing or maintenance evidence.

Package scaffolding

The artifact has no README, tests, or changelog, but the exact version has GitHub release notes and the package is a small compiled PHP library. The missing consumer documentation is still a minor transparency gap.

Release history

The package has only 3 releases and none in the last 12 months; its latest release was about 2 years and 7 months ago. This is meaningful evidence of slowing maintenance, though not abandonment by itself.

Repo commit activity

The repository recorded 0 commits and 0 active maintainers in the last 3 months, consistent with the long release gap. This reduces confidence that issues or compatibility changes will be addressed promptly.

Repo tooling

Composer build tooling is present, but no security scanning tools were detected. This is a modest hygiene gap rather than evidence that the release is unsafe.