codememory/caching

Release historydanger

The latest release was about five years ago, with zero releases in the last 12 months; only three releases exist overall. This strongly lowers confidence in ongoing maintenance.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers in the last three months, consistent with the long release gap and indicating no observed current maintenance.

Package scaffoldingcaution

A changelog and GitHub release for this version provide some release transparency, but the README is only nine characters and the repository has no tests. The missing tests are not inherently a packaging defect, while the extremely thin documentation limits consumer confidence.

Repo popularitycaution

The repository has zero stars and forks and only one watcher. Popularity is supporting evidence rather than a verdict, but these counts provide no meaningful evidence of an active user or contributor base.

Repo toolingcaution

Composer build tooling is present, but no security-scanning tooling was detected. This is a hygiene gap that adds some uncertainty without independently making the package unfit.