los/api-problem

Release historydanger

The package has had no registry release for over 9 years, despite seven releases overall. This is a substantial maintenance concern for a dependency, even though the repository has recent activity.

Repo bus factorcaution

All recent repository commits came from one contributor, leaving maintenance dependent on a single active person and increasing continuity risk.

Repo commit activitycaution

The repository recorded one commit in the last 3 months from one active maintainer, providing some current activity but only weak evidence of sustained maintenance.

Repo toolingcaution

Composer build tooling is present, but no security-scanning tooling was detected. The missing scanning is a transparency and hygiene gap, not evidence that the package is unsafe.

Security policycaution

The repository has no published security policy, making vulnerability reporting and response expectations less clear for adopters.