tualo/whiteboard

The MIT license, matching repository, and organization backing provide clear ownership and provenance. Its single runtime dependency keeps adoption simple, but the consumer documentation is extremely sparse and recent maintenance is limited.

Latest 1.0.3

Packagist

58%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Package scaffolding

A README is present, but it contains only 19 characters and offers little guidance for consumers. Missing tests and changelog files are normal for a published artifact and are not treated as gaps here.

Release history

The package has three releases over 449 days, with only one release in the last 12 months and the latest release about 11 months ago. This indicates a small and slowing release history, though it is not abandonment by itself.

Repo commit activity

The repository recorded zero commits and zero active maintainers in the last three months. This is a meaningful maintenance concern for a package consumers may need updated or repaired.

Repo tooling

Composer is used as the build tool, which fits the package ecosystem, but no security-scanning tooling is present. The missing scanner is a hygiene gap rather than evidence that the package is unsafe.

Security policy

The repository has no security policy. This weakens vulnerability-reporting transparency, though it is a moderate governance gap rather than a severe dependency risk on its own.