lifo/remote-control

The MIT license, clear README, and small dependency set help consumers understand and install it. Its low activity and absent security process leave long-term fixes and oversight uncertain.

Latest v1.0

Packagist

38%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

Only one release exists, published nearly ten years ago, with no releases in the last 12 months. This is strong evidence of abandonment for a dependency intended for ongoing use.

Repo commit activity

The repository has had no commits and no active maintainers in the last three months, consistent with the long release gap and leaving little evidence of current maintenance.

Maintainers

One registry publishing account is listed. Because the repository is user-owned rather than organization-backed, this indicates a thin visible maintainer base, though registry access alone does not prove inactivity.

Repo popularity

The repository has only 3 stars, 1 fork, and 1 watcher. Low popularity is supporting evidence of limited adoption, but does not independently establish poor health.

Repo tooling

Composer build tooling is present, but no security scanning tools are configured. This is a hygiene gap that adds concern alongside the lack of maintenance.