Package Health/immachakata/ci4-relationships

immachakata/ci4-relationships

The small scope, MIT license, clear README, and release notes make the package straightforward to evaluate. However, it has had no release in over two years, no recent commits, no tests, and no security scanning, so ongoing maintenance is uncertain.

Latest v1.2-alpha.1

Packagist

55%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The package has only three releases and none in the last two years, indicating a prolonged lack of published maintenance. Its age and existing release history provide some maturity, but not enough to offset the current pause.

Repo commit activity

The repository recorded zero commits and zero active maintainers in the last three months, consistent with the long release gap. This reduces confidence that defects or compatibility changes will be addressed promptly.

Repo popularity

The repository has three stars, one fork, and no watchers, showing limited external adoption and review. Popularity is only supporting evidence, but this provides little independent maintenance validation.

Repo tooling

Composer is used for the build, but no security scanning tools are present. That is a transparency and maintenance-hygiene gap for a dependency, though it is not evidence that the package is unsafe.

Security policy

The repository has no security policy, leaving no documented process for reporting or handling vulnerabilities. The small project scope partly limits the significance, but the gap remains relevant to dependency maintenance.