ksnk/text

ksnk/text v1.0.25 appears usable and reasonably transparent: it is a mature MIT-licensed package with a matching repository, documented usage, tests, a small dependency surface, and a current stable release. The main concerns are limited observable maintenance capacity—only one commit from one contributor in the last 3 months—and very low repository adoption, alongside absent security-policy and security-scanning evidence. These concerns warrant caution for long-lived or security-sensitive dependencies, but the package is not deprecated or archived and has no major abandonment indicator.

Latest v1.0.25

Packagist

72%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Maintainers

Only one registry account has publish access. This is not itself evidence of poor maintenance, but it leaves publishing continuity dependent on a single person.

Project backing

The repository is owned by a user rather than an organization, so there is no organizational backing shown to mitigate the single-maintainer continuity risk.

Repo bus factor

All recent commits come from one contributor, giving the repository a bus factor of one and creating a meaningful continuity risk if that maintainer becomes unavailable.

Repo commit activity

Only one commit was made in the last 3 months by one active maintainer. The recent commit is positive evidence of activity, but the low volume indicates limited observable maintenance capacity.

Repo popularity

The repository has zero stars and forks and only one watcher, so there is little external adoption or community visibility to compensate if maintenance stops.