jorisros/nginxparser

The MIT license, working tests, and matching repository improve transparency. Unpinned workflow actions and no security policy weaken maintenance hygiene, while the project shows little recent activity.

Latest 1.1

Packagist

42%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The package has only one release, published about 10 years ago, with no releases in the last 12 months. This is strong evidence of low maintenance activity.

Repo commit activity

There were zero commits and zero active maintainers in the last three months. Combined with the old latest release, this indicates a material abandonment risk.

Project backing

The registry namespace and repository are owned by the same individual, so the package has direct ownership continuity, but it lacks organizational backing that could compensate for a thin maintainer base.

Repo issue activity

There were no new or closed issues or pull requests in the last month, while three issues and one pull request remain open. This suggests limited ongoing project attention.

Repo tooling

Composer build tooling is present, but no security scanning tools were detected. The missing scanning is a modest repository hygiene gap rather than a standalone adoption blocker.