keven/jobijoba-client

The README provides clear installation and usage guidance, and the MIT license is declared. The project has no security scanning or policy, which limits transparency when maintenance is already uncertain.

Latest 1.0.1

Packagist

58%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Project backing

The repository is owned by an individual user rather than an organization. That is not inherently unhealthy, but it provides less visible organizational backing for long-term maintenance.

Release history

The package has only two releases, both published on the same day, and no releases in the last 12 months; the latest release was about 1 year and 11 months ago. This indicates a small, inactive project and raises maintenance risk.

Repo popularity

The repository has zero stars and forks and only one watcher. Popularity is supporting evidence rather than a verdict, but these figures provide little evidence of a broad active community.

Repo tooling

Composer is used for builds, but no security scanning tool is configured. For a small library this is a modest transparency and maintenance gap, not a severe risk on its own.

Security policy

The repository has no security policy. This weakens disclosure transparency, although the package's small scope and lack of other severe indicators keep it from being a standalone adoption blocker.