alex-kalanis/kw_paging

Clear licensing, a real README, repository tests, and release notes make the package easier to evaluate. Its build uses eight unpinned actions and the repository has no security policy. The absence of releases and commits for about two and a half years raises maintenance risk.

Latest v2.0.0

Packagist

62%

Total Score

Maintainer Stability

Maturity

Supply Chain

Health Score Breakdown

Release history

The latest release was about two and a half years ago, with no releases in the last 12 months and a median interval of about 321 days. This is meaningful abandonment risk despite six releases over the package's lifetime.

Repo commit activity

There were no commits and no active maintainers in the last three months, consistent with the long gap since the last release. This weakens confidence that defects or compatibility issues will be addressed.

Repo tooling

Composer build tooling is present, but no security scanning tools were detected. The missing scanning is a modest transparency and maintenance gap, not evidence of malicious behavior.

Security policy

The repository has no security policy. For a small pager library this is a limited transparency gap, but it leaves vulnerability reporting and response expectations unclear.

Workflow audit

The single workflow was fully analyzed with no untrusted checkout, injection, or high-severity findings, and it avoids top-level write permissions. However, all 8 action references are unpinned, leaving avoidable build-integrity risk.