rancoud/security

The package has clear documentation, repository tests, a recent release, and a security policy. Its maintenance capacity is thin, with one registry maintainer and no commits in the last three months; workflow references are also unpinned.

Latest 4.0.3

Packagist

68%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Maintainers

Only one account has registry publishing access. The repository is user-owned rather than organization-backed, so this indicates concentrated publishing and maintenance capacity.

Repo commit activity

The repository recorded zero commits and zero active maintainers in the last three months. Although a release was published recently, the absence of recent commit activity is a meaningful maintenance concern.

Repo issue activity

There are no open issues or pull requests and no issue or pull-request activity in the last month. This is consistent with a quiet project but does not by itself prove abandonment.

Repo popularity

The repository has 0 stars, 2 forks, and 1 watcher. This provides little evidence of community review or a broad maintainer base, but popularity is supporting evidence rather than a verdict.

Repo tooling

Composer is used for the build, but no security-scanning tool was detected. For a security-focused library, that is a transparency and maintenance gap.