Package Health/robo-meister/context-engine-api

robo-meister/context-engine-api

This is a usable but very early-stage package with good basic transparency: the artifact and repository contain a README and tests, the file trees match, dependencies are minimal and explicit, lifecycle scripts are absent, and the repository is not archived or deprecated. However, the v0.0.2 version, only two releases over 101 days, zero commits and zero active maintainers in the last three months, zero popularity, single-user project backing, and absence of security tooling and a security policy leave meaningful maintenance and resilience uncertainty. It may be reasonable for controlled adoption, but production consumers should expect API instability and verify ongoing maintainer activity.

Latest v0.0.2

Packagist

62%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Project backing

The repository is owned by a user account rather than an organization, so there is no organizational backing signal to offset the thin maintenance base.

Release history

The package is only 101 days old and has two releases separated by about 101 days, so its release and maintenance track record is limited.

Repo commit activity

The repository recorded zero commits and zero active maintainers in the last three months, a significant maintenance concern despite the recent push timestamp and one merged pull request.

Repo issue activity

There are no open issues or pull requests and one pull request was merged in the last month; this is not negative by itself, but the low volume offers limited evidence of sustained community maintenance.

Repo popularity

The repository has zero stars, forks, and watchers. Popularity is supporting evidence rather than a verdict, but these values provide no external adoption or resilience evidence for this young package.