lsr/console

Maintainerscaution

Only one registry account has publish access. This is a real publishing continuity risk because there is no demonstrated backup publisher, although repository activity shows the package is currently maintained.

Project backingcaution

The repository is owned by an individual user rather than an organization, so there is no visible organizational maintenance or handoff support to offset the concentrated maintainer base.

Repo bus factorcaution

All five recent commits come from one contributor, producing a complete single-contributor concentration risk. No organization backing or second active contributor is present to compensate for that dependence.

Repo popularitycaution

One star, no forks, and no watchers provide little external adoption evidence. Popularity is supporting evidence rather than a verdict, so this lowers confidence in maturity but is not by itself a severe health concern.

Repo toolingcaution

Composer build tooling is present, but no security scanning tools are configured. The missing scanning is a hygiene gap rather than evidence of unsafe behavior on its own.