dyweb/redis-cache

Documentation, tests, licensing, and release notes make the package understandable to integrate. Its maintenance appears to have stopped for about ten years, with little community activity and no security policy, so future compatibility and support are uncertain.

Latest v0.2.1

Packagist

38%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The package made three releases over two days in August 2016, then had no releases in the following ten years. This strongly suggests abandonment despite the package having reached a published release.

Repo commit activity

The repository shows no commits and no active maintainers in the last three months, while its last push was about ten years ago. This is strong evidence that maintenance has stopped.

Repo issue activity

There were no new or closed issues or pull requests in the last month, with one issue still open. This indicates little current community or maintainer activity, though the small project size limits how much popularity should matter.

Repo tooling

Composer build tooling is present, but no security scanning tools were detected. The missing scanning is a hygiene gap, made more relevant by the project's long period without maintenance.

Security policy

The repository has no security policy. For a cache library that may handle application data, this reduces transparency about how vulnerabilities should be reported and handled.