rtippin/janus-client

The package has a clear MIT license, a substantial README, repository tests, and no install-time scripts. Its small scope and clean workflow audit help, but security scanning is absent and action references are unpinned.

Latest v1.4.0

Packagist

62%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Maintainers

Only one registry account has publish access, which creates a limited publishing bus factor. The linked repository is user-owned rather than organization-backed, so no compensating organizational signal is present.

Project backing

The registry namespace and repository are owned by the same individual, and the repository owner is a user rather than an organization. This is consistent ownership but provides limited evidence of broader project backing.

Release history

The latest release was published in March 2025, with no releases in the following 12 months of recorded history. The package has 10 releases over roughly five years, but the recent pause raises maintenance risk.

Repo commit activity

There were zero commits and zero active maintainers during the last three months of observation. Combined with the release pause, this is evidence of slowed maintenance rather than merely a quiet registry.

Repo tooling

The repository uses Composer but has no security-scanning tools. For a small package this is a transparency and maintenance gap, though it is not evidence that the release is unsafe by itself.