nostriphant/client

Tests, a clear README, and no install-time scripts make adoption straightforward. Maintenance is concentrated in one contributor, while the repository lacks a security policy and has one unpinned workflow action. Organization backing and recent activity reduce, but do not remove, that continuity risk.

Latest 3.0.0

Packagist

80%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Repo bus factor

All eight recent commits came from one contributor, creating a real continuity risk if that maintainer becomes unavailable. Organization backing provides some capacity for handoff, but no second active contributor is shown.

Repo tooling

Composer build tooling is present, but no security-scanning tool was detected. This is a modest transparency gap rather than evidence of unsafe code.

Security policy

The repository has no security policy, leaving vulnerability-reporting expectations unclear for consumers of a network client.

Workflow audit

The sole workflow was fully analyzed with no high- or medium-confidence findings and no untrusted checkout or script injection. Its one action is unpinned, which is a supply-chain hygiene gap, while the absence of a top-level permissions block is acceptable on its own.