orchid/crud

Its long release history and stable 4.x line provide useful confidence. Recent repository silence, inactive issue handling, and an unpinned container image reduce confidence in ongoing maintenance and build hygiene.

Latest 4.4.0

Packagist

62%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Repo commit activity

The repository recorded zero commits and zero active maintainers in the last three months, which is a concrete sign of currently stalled maintenance.

Release history

The package has existed since December 2020 with 36 releases and a median interval of about 10 days, but it has had no registry release in the last 12 months. The established history is positive, while the current pause is a maintenance caution.

Repo issue activity

There were no new or closed issues or pull requests in the last month, with 23 open issues and 4 open pull requests remaining. This indicates limited recent project responsiveness.

Repo tooling

Composer build tooling is present, but no security-scanning tooling was detected. The missing scanning is a hygiene gap rather than evidence that the release is unsafe.

Workflow audit

Both workflows were analyzed without trigger or script-injection issues, but all five action references are unpinned and the audit found a high-confidence unpinned container image. This weakens CI reproducibility and supply-chain hygiene.