domainparser/php

The repository is organization-backed and matches the package, while MIT licensing and no install scripts reduce adoption friction. Documentation and verification practices are thin, so future maintenance and integration support are uncertain.

Latest v1.0.0

Packagist

58%

Total Score

Maintainer Stability

100

Maturity

Supply Chain

Health Score Breakdown

Package file tree

The package and repository each contain only README.md and composer.json. That minimal structure may be adequate for a very small library, but provides little transparency into implementation or verification.

Package scaffolding

The artifact includes a README, but it is only five characters long and there are no tests or changelog. Missing tests and changelog are normal for published artifacts, but the nearly empty README limits consumer guidance.

Release history

This is the only release, published nearly three years ago, with no releases in the last 12 months. That weakens evidence of ongoing maintenance.

Repo tooling

Composer is used for builds, but no security scanning tools are present. This is a modest verification gap rather than evidence that the release is unsafe.

Security policy

The repository has no security policy. For a small package this is a transparency and reporting gap, though it is not by itself evidence of abandonment.