los/los-api-client

Release historydanger

The latest registry release was published nearly eleven years ago, with only four releases and none in the past year. This is strong evidence of a dormant release line despite the repository being recently updated.

Project backingcaution

The repository is owned by an individual user rather than an organization, so the single-maintainer and single-contributor findings are not visibly backed by a larger project structure.

Repo bus factorcaution

All recent commits came from one contributor, giving the repository a complete single-contributor concentration. The linked owner is an individual rather than an organization, so there is no provided backing signal to compensate for that concentration.

Repo commit activitycaution

Only one commit was recorded in the past three months, with one active maintainer. This indicates very limited current maintenance capacity.

Repo toolingcaution

Composer build tooling is present, but no security-scanning tooling was detected. This is a modest transparency and maintenance gap rather than a severe risk on its own.