ian-ozzie/html

The project is small and recently active, with tests, a clear license, and no install-time scripts. Its long-term resilience is limited by one contributor, absent security scanning, and workflow actions that are all unpinned.

Latest 6.0.1

Packagist

72%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Project backing

The registry namespace and repository owner match, but both identify an individual user rather than an organization. This is consistent ownership evidence, while offering less maintenance redundancy.

Repo bus factor

One contributor made 100% of the 7 commits in the last 3 months. Because the project is user-backed rather than organization-owned, this concentration is a meaningful continuity risk.

Repo commit activity

The repository recorded 7 commits in the last 3 months, all from one active maintainer. The activity is recent, but the narrow contributor base limits resilience.

Repo tooling

Composer build tooling is present, but no security-scanning tools were detected. The missing scanning is a modest transparency and maintenance gap, not evidence of a vulnerability.

Security policy

The repository has no security policy. For a small HTML-generation library this is a transparency gap, though it is less significant than absent maintenance activity or an archived repository.