abuseio/parser-common

Usable with caveats: it has a long release history, a current stable release, clear licensing, and matching organization-backed source code. Recent repository activity is quiet, with no commits in three months and no security policy, so verify maintenance before making it a core dependency.

Latest 5.0.1

Packagist

72%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Package scaffolding

A README is present, although it is only 16 characters long and provides almost no consumer guidance. Missing tests and changelog files in the published artifact are normal packaging practice, while the repository also reports no tests or changelog.

Repo commit activity

The repository had zero commits and zero active maintainers in the last three months, a meaningful maintenance concern even though a recent release was published.

Repo tooling

Composer is used as a build tool, but no security-scanning tools are configured. This is a transparency and assurance gap, though it is not by itself evidence of abandonment.

Security policy

The repository has no security policy, leaving no documented process for reporting or handling vulnerabilities.