Package Health/briceburg/silverstripe-pickerfield

briceburg/silverstripe-pickerfield

The source repository matches the package, remains available, and provides a useful README with a clear BSD-3-Clause license. No security policy or automated security scanning is present, leaving maintenance and disclosure practices less transparent.

Latest 0.9.0

Packagist

52%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The package has only one registry release, published about 10 years ago, with no releases in the last 12 months. This is strong evidence of limited ongoing maintenance, although the repository was pushed more recently.

Repo commit activity

There were zero commits and zero active maintainers in the last three months. Combined with the single old registry release, this indicates a meaningful risk of stalled maintenance.

Project backing

The registry namespace and repository are owned by the same individual account. This confirms ownership alignment but provides limited organizational backing for long-term maintenance.

Repo issue activity

The repository has six open issues and two open pull requests, but recorded activity in the last month is zero for both issues and pull requests. This supports the maintenance concern without proving abandonment by itself.

Repo tooling

Composer is used as a build tool, but no security scanning tool is configured. The missing scanning reduces repository hygiene and transparency, though it is not by itself evidence that the package is unsafe.