draw/contracts

Usable with caveats: it has a long release history, frequent recent releases, and an active repository. Adoption carries some maintenance risk because all recent commits come from one contributor and the package and repository contain no tests, README, or changelog.

Latest 0.43.0

Packagist

72%

Total Score

Maintainer Stability

Maturity

Supply Chain

Health Score Breakdown

Package scaffolding

The artifact and repository have no README, tests, or changelog. For a small abstractions-only package this is a meaningful transparency and maintenance gap, with no provided repository documentation or tests to compensate.

Project backing

The repository is owned by an individual user rather than an organization, so the single-contributor pattern is not offset by visible organizational backing.

Repo bus factor

One contributor made all 3 commits in the last 3 months, leaving maintenance highly concentrated and creating a real continuity risk for this individually owned project.

Repo popularity

The repository has zero stars and forks and one watcher. This is weak supporting evidence, but popularity is not decisive for a small focused package.

Repo tooling

Composer is used as a build tool, but no security scanning tools are reported. The missing scanning is a transparency gap, though it is not by itself evidence of unsafe code.