opine/collection

Documentation, tests, release notes, and a matching repository provide useful transparency. However, the project has had no release or commit activity for nearly 12 years, with no security scanning or published security policy.

Latest 2.0.8

Packagist

35%

Total Score

Maintainer Stability

Maturity

Supply Chain

Health Score Breakdown

Release history

The latest release was in December 2014, and there have been no releases in the last 12 months. This is strong evidence of abandonment for a package intended as a maintained application dependency.

Repo commit activity

The repository recorded zero commits and zero active maintainers in the last three months, consistent with the package's nearly 12-year release gap. The repository is not archived, but that does not offset the lack of observed maintenance.

Repo issue activity

Three issues remain open, with no issues or pull requests opened or closed in the last month. This indicates unresolved maintenance demand without recent project response.

Repo tooling

Composer build tooling is present, but no security scanning tools were detected. For a package exposing a REST API and relying on 15 runtime dependencies, this is a meaningful maintenance gap.

Security policy

The repository has no security policy. That reduces transparency about how consumers should report and receive fixes for security concerns.