vis/esputnik_client_l5

The package is small, clearly documented, correctly licensed, and has a repository that matches its name. Its maintenance and security coverage are weak, so future compatibility and support are uncertain.

Latest 1.1.2

Packagist

38%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The latest release was published in May 2017, with no releases in the last 12 months and no evident ongoing release cadence after four releases. This is strong evidence of abandonment risk for a library dependency.

Repo commit activity

There were zero commits and zero active maintainers in the last three months, consistent with the release history showing no current maintenance. This materially raises abandonment and compatibility risk.

Maintainers

Only one registry account has publish access, indicating limited publishing capacity. The repository is also owned by that individual rather than an organization, so there is no provided backing signal to compensate for the thin maintainer base.

Project backing

The repository is owned by an individual user rather than an organization, so the package has no demonstrated organizational backing to offset its single-maintainer profile.

Repo popularity

The repository has zero stars and forks and only one watcher, providing little supporting evidence of community adoption or external oversight. Popularity is supporting evidence, so this is a secondary concern rather than a verdict.