minkbear/captainhook

The MIT declaration, clear README, and repository tests provide useful transparency for adopters. Maintenance appears to have stopped for about seven years, with no recent commits or releases, so pinning this package carries substantial abandonment risk.

Latest 3.4.4

Packagist

43%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The latest release was published in April 2019, with no releases in the last 12 months and 26 releases overall. The long period without a release is strong evidence of abandonment risk.

Repo commit activity

The repository recorded zero commits and zero active maintainers in the last three months, consistent with the roughly seven-year release gap. No provided maintenance signal compensates for this inactivity.

Repo issue activity

There was no issue or pull request activity in the last month, and no pull requests were open. This reinforces the picture of an inactive project, although the issue count itself is unknown.

Repo popularity

The repository has zero stars and forks and one watcher. Popularity is only supporting evidence, but these figures provide little community signal to offset the lack of maintenance.

Repo tooling

Composer build tooling is present, but no security scanning tools were detected. The missing scanning is a modest hygiene gap rather than evidence that the package is unsafe.