drinks-it/sf-cache-client

Release historydanger

The latest release was over five years ago, and there have been no releases in the last 12 months. This strongly indicates abandonment risk despite the package having three historical releases.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers over the last three months, consistent with its last push being over five years ago. No provided maintenance signal compensates for this inactivity.

Package scaffoldingcaution

The package includes a README, but it is only 17 characters long and provides almost no usage guidance for a cache client. The absence of tests and a changelog is not itself a packaging gap, but the documentation is materially thin.

Repo toolingcaution

Composer is used as the build tool, which is appropriate, but no security-scanning tooling is present. This is a secondary transparency and maintenance concern rather than evidence that the release is unsafe.

Security policycaution

The repository has no security policy, leaving no documented process for reporting or handling vulnerabilities. This adds a modest transparency concern to an already inactive project.