relewise/client

This is a healthy, actively maintained release with a consistent release cadence, a stable non-prerelease version, recent repository activity from four maintainers, organizational backing, tests, a clear MIT license, and no deprecation or install-time lifecycle scripts. The main concerns are incomplete repository security hygiene: no security policy, several workflows without top-level token permissions, and one workflow with top-level write permissions. Repository popularity is low, but the active maintenance and organizational ownership provide stronger evidence of dependency health than popularity counters; the absent changelog is also mitigated by GitHub Releases and regular publishing.

Latest 2.19.0Packagist

Health Score Breakdown

Repo popularitycaution

The repository has 0 stars and 0 forks, indicating limited public adoption evidence; this is only a supporting concern because recent commits, releases, and organizational backing demonstrate active maintenance.

Security policycaution

The repository has no security policy, leaving vulnerability-reporting guidance and disclosure expectations unspecified.

Token permissionscaution

Three of four workflows lack top-level token permissions and one workflow declares top-level write permissions, which is weaker least-privilege hygiene even though no dangerous workflow behavior was detected.

View all 19 health checks

Vulnerabilities

We didn't find any vulnerabilities for this package.