ekrembk/flysystem-backblaze

Release historydanger

The package has had no release in about 8 years, with zero releases in the last 12 months. This is strong evidence of abandonment despite its established release history.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers in the last 3 months, providing no evidence of current maintenance capacity.

Repo toolingcaution

Composer is used for builds, but no security-scanning tools are configured. For a package that handles storage credentials and API integration, this is a meaningful transparency gap.

Security policycaution

The repository has no security policy, leaving no documented channel or process for reporting security issues. This reinforces the maintenance concerns, though it does not by itself make the release unfit.