diegovilarinho/on-hand

It includes repository tests, an MIT license, and no install-time scripts, which reduce adoption friction. Its two runtime dependencies are explicit, but no security scanning or security policy is provided.

Latest 1.0.0

Packagist

38%

Total Score

Maintainer Stability

Maturity

Supply Chain

Health Score Breakdown

Release history

The package has made only one release, on July 19, 2017, with no releases in the last 12 months. This leaves the release line about 9 years without evidence of ongoing maintenance.

Repo commit activity

There were zero commits and zero active maintainers in the last 3 months. Combined with the last repository push in 2017, this indicates a long-standing lack of observed maintenance capacity.

Project backing

The repository is owned by an individual user rather than an organization. That does not establish abandonment by itself, but it provides less visible backing for a project with no recent activity.

Repo issue activity

There are no open issues or pull requests and no recent issue or pull-request activity. This is mildly reassuring about unresolved workload, but it does not compensate for the complete absence of recent commits.

Repo tooling

Composer is used as a build tool, but no security scanning tool is configured. The lack of scanning is a transparency and maintenance-hygiene gap, though it is less severe than the inactive release and commit history.