kamilz/b2backblaze

Release historydanger

The latest release was over 9 years ago, with no releases in the past 12 months. This is strong evidence of abandonment for a library that integrates with an external storage API.

Repo commit activitydanger

There were no commits and no active maintainers in the past 3 months. Combined with the last push being over 8 years ago, this is strong evidence of abandonment.

Repo issue activitycaution

There are two open issues and no issue or pull-request activity in the past month. This suggests the project is not actively maintained, though the issue count itself is small.

Repo toolingcaution

Composer is used for the build, but no security-scanning tools are present. The missing scanning is a hygiene gap rather than evidence that the package is unsafe.

Repository archivedcaution

The repository is not archived, but it was last pushed over 8 years ago. The non-archived status is a limited positive and does not remove the abandonment concern.