bagart/ask-client

This is a usable but very young package with solid basic transparency: it has an MIT license, a substantial README, tests in the repository and artifact, a coherent 167-file source tree, no install-time lifecycle scripts, and it is not deprecated or archived. However, the package is only 9 days old with two releases, is still on the 0.x line, and all 9 commits in the last 3 months come from one contributor; this leaves maintenance continuity and bus-factor risk unresolved. The repository also has no security policy or security scanning, while its zero popularity and lack of issue activity provide little independent evidence of maturity. Depend on it only if its early-stage status and single-maintainer risk are acceptable.

Latest v0.1.1

Packagist

58%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Maintainers

Only one registry account has publish access. That is not proof of poor maintenance, but without organization backing it provides limited publishing redundancy.

Project backing

The repository owner is the user account bagart, not an organization, so there is no provided evidence of institutional backing to compensate for the single-maintainer concentration.

Release history

The package is only 9 days old and has two releases, with both releases occurring within roughly 12 hours. This is insufficient history to establish long-term maintenance reliability.

Repo bus factor

One contributor made all 9 recent commits, giving a 100% top-contributor share. With the owner identified as a user rather than an organization, this is a meaningful continuity and abandonment risk.

Repo commit activity

The repository recorded 9 commits in the last 3 months, showing active initial development. Because the package is only 9 days old, this does not yet demonstrate sustained maintenance.