spsostrov/app-console

The package has clear documentation, a declared MIT license, and a small dependency surface. Single-person ownership, no commits in the last three months, and no repository security policy leave maintenance capacity and security transparency uncertain.

Latest v0.6.2

Packagist

70%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Maintainers

Only one registry account has publishing access, and the linked repository is owned by an individual rather than an organization. This leaves limited visible publishing and maintenance redundancy.

Project backing

The package and repository are backed by an individual owner, so there is no organizational maintenance backing shown by this signal.

Repo commit activity

The repository recorded no commits and no active maintainers in the last three months. The recent release partly offsets this, but the short-term development pause still raises maintenance risk.

Repo popularity

The repository has no stars or forks and only one watcher. Popularity is not required for a small package, but these counters provide little independent evidence of community support.

Repo tooling

Composer build tooling is present, but no security scanning tools were detected. This is a transparency and hygiene gap rather than evidence that the package is unsafe.