ariedeha/xctx

Usable with caveats: the package is well-documented, tested, licensed, and its repository matches the package, but it is very young and has had no commits or active maintainers in the last three months. Zero adoption signals and no security policy add uncertainty for a security-sensitive library.

Latest 0.3.2

Packagist

62%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Maintainers

One registry publishing account provides a thin maintainer base, which limits redundancy; the individual repository ownership is consistent with that account but does not compensate for the narrow bus factor.

Project backing

The registry namespace and repository owner correspond, but the project is backed by an individual rather than an organization, leaving limited institutional continuity.

Release history

The package is only about 11 months old and has just two releases, so its maintenance record is still limited despite the short three-day interval between those releases.

Repo commit activity

The repository recorded zero commits and zero active maintainers in the last three months. For a young package this is a meaningful maintenance concern, even though the latest push was near the latest release.

Repo issue activity

There are no open issues or pull requests and no activity in the last month; while this avoids an unresolved backlog, it also provides little evidence of an engaged user or maintainer community.