beeline/yii2-tiered-cache

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers in the last three months. This is concrete evidence that current maintenance has paused and increases abandonment risk.

Project backingcaution

The package registry namespace and repository owner are different user-owned identities, so there is no clear organization backing to compensate for the thin maintainer and inactive commit signals.

Release historycaution

Seven releases arrived within the first two days, followed by no further registry releases over roughly ten months. That burst provides some initial maturity evidence but little evidence of sustained release maintenance.

Security policycaution

No repository security policy was found. This is a transparency gap for a package that handles cache infrastructure, although it does not by itself show abandonment.

Workflow auditcaution

The only workflow was fully analyzed with no dangerous triggers, untrusted checkouts, or audit findings, but all four action references are unpinned. The lack of a top-level permissions block is acceptable on its own, while unpinned actions remain a supply-chain hygiene weakness.