Package Health/robo-meister/flow-scribe-api

robo-meister/flow-scribe-api

This is a usable but very young package with solid basic hygiene: the artifact includes a README, tests, changelog, and a coherent 11-file tree, while the repository was updated recently, is not archived, is not deprecated, and uses read-only workflow permissions without the analyzed dangerous workflow patterns. However, the release is only 97 days old, remains at v0.0.3, has just one commit and one active contributor in the last three months, and has no security policy or security-scanning tooling. The proprietary manifest license also gives less transparency and reuse clarity than a standard open-source license. It may be reasonable for controlled adoption, but its maturity and maintainer-bus-factor risks warrant pinning the version and monitoring the repository.

Latest v0.0.3

Packagist

68%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

License

The package declares a proprietary license in its manifest, so it is licensed, but the absence of a license file provides less transparency and may impose less familiar reuse constraints than a standard open-source license.

Project backing

The repository is owned by a user rather than an organization, so there is no provided organizational backing to compensate for the package's concentrated contributor base.

Release history

The package is only 97 days old with three releases and a median interval of about 49 days, so there is some release activity but limited evidence of long-term maintenance maturity.

Repo bus factor

All recent commits come from a single contributor with a 100% share, creating a significant continuity risk for a young package.

Repo commit activity

Only one commit from one active maintainer occurred in the last three months. The recent repository push is encouraging, but this still indicates thin observed maintenance capacity.