day4/blubrry-sdk

Release historydanger

This is the only release, published nearly six years ago, with no releases in the last 12 months. That strongly raises abandonment risk despite the stable version designation.

Repo commit activitydanger

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

Repo package mentioncaution

The repository name does not match the package name and its README does not mention the package. That creates uncertainty about whether the linked source repository actually belongs to this package.

Repo toolingcaution

Composer build tooling is present, but no security scanning tools were detected. This is a modest maintenance and assurance gap for a package handling API authentication.

Security policycaution

The repository has no security policy. For an API SDK, this is a transparency and vulnerability-reporting gap, although it does not by itself show that the package is unsafe.