imedge/redis-runner

Release historydanger

Only two releases were published, both within one week, and there have been no releases in over two years. This is strong evidence of a small or inactive project and lowers confidence in ongoing maintenance.

Repo commit activitydanger

The repository recorded no commits and no active maintainers in the last three months, consistent with the release gap of over two years. This materially increases abandonment risk.

Package scaffoldingcaution

The package includes tests, and the missing changelog is normal packaging practice. However, its README is only 14 characters long, leaving library consumers with almost no usage guidance.

Repo toolingcaution

Composer build tooling is present, but no security scanning tools were detected. For a small library this is a modest transparency and maintenance gap rather than a severe risk.

Security policycaution

The repository has no security policy, so there is no stated process for reporting or handling vulnerabilities. This is a documentation gap that matters for a dependency but does not independently make the release unfit.