sinkcup/laravel-filesystem-cos-updated

Release historydanger

The package has had only one release, published about five years ago, with no releases in the last 12 months. This is strong evidence of abandonment risk for a dependency.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers over the last three months, consistent with the release history showing no activity for about five years.

Repo package mentioncaution

The linked repository name does not match the package name and its README does not mention the package. That raises concern that the repository may not clearly belong to this release.

Repo toolingcaution

Composer is used as a build tool, but the repository has no security scanning tools. This limits automated oversight, although it is secondary to the much older maintenance signals.

Security policycaution

The repository has no security policy, leaving no documented channel or process for reporting vulnerabilities. This is a transparency gap for a package handling cloud-storage credentials.