trebel/schematic

The package is clearly identified, MIT-licensed, documented, and has only one runtime dependency. Its small scope helps, but nearly four years without another release or repository commit leaves maintenance and compatibility risk.

Latest 1.0

Packagist

45%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

This is the only release, published nearly four years ago, with no releases in the last 12 months. That is strong evidence of a stagnant project.

Repo commit activity

There were no commits and no active maintainers in the last three months, consistent with the long release gap and indicating a high abandonment risk.

Project backing

The repository is owned by an individual account, so the single registry maintainer does not benefit from visible organizational backing.

Repo issue activity

There are no open issues or pull requests and no recent issue activity. While this is not inherently unhealthy, it offers no evidence of an active user or maintainer community.

Repo popularity

The repository has no stars or forks and only one watcher. This provides little external evidence of adoption or review, though popularity is supporting evidence rather than a verdict.