juzaweb/html-dom

The project is clearly licensed, has release notes, and uses no install-time scripts. Its small scope helps, but documentation and security-process coverage are limited.

Latest 1.0.0

Packagist

55%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Package scaffolding

The package has no README, which is a documentation gap for a library consumers must integrate, although its changelog and release notes document the initial release.

Release history

This is the package's only release, published about 16 months ago, with no releases in the last 12 months. That limited history leaves maintenance continuity unproven.

Repo commit activity

The repository recorded no commits and no active maintainers in the last 3 months, despite the project being only about 16 months old. This is a meaningful maintenance concern.

Repo tooling

Composer is used for the build, but no security-scanning tooling is present. This is a modest hygiene gap rather than evidence of unsafe code.

Security policy

The repository has no security policy. For a small library this is not severe, but it reduces transparency about how vulnerabilities would be reported and handled.