tes/laravel-google-drive-storage

Maintainerscaution

Only one individual account has registry publishing access, creating a limited operational base. The matching user-owned repository and recent release provide some evidence of direct ownership but do not remove the single-maintainer risk.

Project backingcaution

The repository is owned by an individual rather than an organization, so there is no organizational backing to compensate for the thin maintainer base.

Release historycaution

The package is about two years old with three releases and one release in the last 12 months; this shows some ongoing maintenance, but the roughly six-month median release interval is modest.

Repo commit activitycaution

The repository recorded zero commits and zero active maintainers in the last three months. Although the recent release provides some compensating evidence, the lack of current activity raises maintenance risk.

Repo toolingcaution

Composer build tooling is present, but no security-scanning tools were detected. For a small package this is a transparency gap rather than a severe risk, especially since no dangerous workflows were found.