Package Health/yoelpc4/laravel-cloudinary

yoelpc4/laravel-cloudinary

Tests, documentation, licensing, and release notes make integration straightforward. The repository is not archived and has no audited workflow findings, but it lacks a security policy and uses three unpinned actions.

Latest v6.0.0

Packagist

62%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Maintainers

One registry publishing account is listed, while the repository owner is an individual rather than an organization. This leaves a thin visible maintenance base for a package with no recent commits.

Project backing

The package and repository are owned by the same individual, so the source appears aligned with the published package, but there is no organization backing to offset the thin maintainer base.

Release history

The package has nine releases since March 2020, but none in the last 12 months and the latest release was about 17 months ago. This indicates materially slowed maintenance for a framework integration package.

Repo commit activity

There were no commits and no active maintainers in the last three months. Combined with the long registry release gap, this raises abandonment risk.

Repo tooling

Composer build tooling is present, but no security scanning tools were detected. This is a modest transparency and maintenance gap, not evidence that the release is unsafe.

Vulnerabilities

We didn't find any vulnerabilities for this package.

Package versions

Maintainers

Yoel Peter Chandra

Direct Dependencies

Dependency	Last Release	Score
illuminate/http Version ^11.0\|^12.0	—	—
league/flysystem Version ^3.29.1	—	—
illuminate/support Version ^11.0\|^12.0	—	—
illuminate/contracts Version ^11.0\|^12.0	—	—
illuminate/filesystem Version ^11.0\|^12.0	—	—