dudu54/laravel-chunk-upload

Release historydanger

The latest release was about 5 years 7 months ago, with no releases in the last 12 months. The 38-release history shows an established package, but the prolonged release silence is a substantial maintenance concern.

Repo commit activitydanger

There were no commits and no active maintainers in the last three months, consistent with the repository's last push being about 5 years 7 months ago. This is strong evidence of abandonment risk.

Maintainerscaution

Only one account has registry publish access, leaving little publishing redundancy. The single-person ownership context increases continuity risk when combined with the absence of recent activity.

Project backingcaution

The repository is owned by an individual rather than an organization, so there is no visible organizational backing to offset the single-maintainer and inactivity concerns.

Repo toolingcaution

Composer build tooling is present, but no security-scanning tools were detected. That leaves a transparency and maintenance-hygiene gap for a package with no recent activity.