niirrty/niirrty.config

Clear documentation, tests, release notes, and licensing support adoption. The small maintainer base and lack of a security policy reduce confidence in long-term support.

Latest 0.6.2

Packagist

61%

Total Score

Maintainer Stability

Maturity

Supply Chain

Health Score Breakdown

Maintainers

Only one registry publishing maintainer is listed, and the project backing identifies an individual owner rather than an organization. This creates a thin support base if that maintainer becomes unavailable.

Release history

The package has nine releases since June 2018, but none in the last 12 months and the latest was published in February 2024. This indicates a mature but currently inactive release cadence.

Repo commit activity

The repository had no commits and no active maintainers in the last three months, consistent with the long gap since the latest release. That weakens evidence of ongoing maintenance.

Repo tooling

Composer is used for the build, but no security scanning tools were detected. The absence of scanning reduces automated security hygiene evidence without indicating that the release is unsafe.

Security policy

The repository has no security policy, leaving vulnerability reporting and response expectations undocumented. This is a transparency gap, though it is less serious than evidence of an archived or deprecated project.