reginaldojunior/winners

There is no security policy or repository security scanning, leaving maintenance processes less transparent. The package includes a README, tests, changelog, MIT licensing, and no install-time scripts.

Latest 1.21.0

Packagist

58%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The package has 73 releases, but none in the last 12 months; its latest release was nearly three years ago. This is a meaningful maintenance concern despite the long release history.

Repo commit activity

The repository recorded 0 commits and 0 active maintainers in the last three months, indicating no recent development activity. The repository is not archived, but that does not offset the current inactivity.

Repo issue activity

There are 20 open issues, with no new or closed issues and no pull-request activity in the last month. This suggests limited ongoing issue management.

Repo tooling

Composer and Phing are used for builds, which supports repeatable project maintenance, but no security scanning tools were detected. The build support partly compensates for the missing security controls.

Security policy

The repository has no security policy, so there is no documented process for reporting and handling vulnerabilities. This lowers transparency but is not severe on its own.