nathanmac/parser

The package has a clear MIT license, a useful README, repository tests, and a small runtime dependency set. Its single-user ownership and lack of security policy leave less oversight if maintenance needs resume.

Latest v4.3

Packagist

52%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The latest release was in September 2016, roughly 10 years ago, despite 27 historical releases. This is strong evidence of stale published maintenance and materially raises abandonment risk.

Repo commit activity

The repository recorded zero commits and zero active maintainers in the last three months. Combined with the old latest release, this points to very weak current maintenance capacity.

Project backing

The registry and repository are owned by the same individual account rather than an organization. That is consistent ownership, but it also means the project has limited visible institutional backing.

Repo issue activity

There were no new or closed issues or pull requests in the last month, with nine open issues and three open pull requests. This indicates limited current project interaction and adds to the maintenance concern.

Repo tooling

Composer is used for the build, but no security scanning tools were detected. The missing scanning is a modest transparency and hygiene gap, not evidence that the package is unsafe.