Package Health/maccesar/laravel-dropzone-enhanced

maccesar/laravel-dropzone-enhanced

This release appears suitable to depend on, with strong signs of active development and release discipline: it is a stable v4 release, has 47 releases over roughly 513 days including 26 in the last 12 months, and the repository had 19 commits in the last three months. The package and repository include a substantial README, tests, changelog, license, and coherent source tree, while the repository is active and not archived. The main risks are single-person maintenance and commit concentration, very low adoption indicators, and the absence of security scanning and a security policy. These concerns warrant monitoring and contingency planning, but do not outweigh the demonstrated maintenance and packaging hygiene.

Latest v4.0.1

Packagist

78%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Maintainers

Only one registry account has publish access. This is a genuine continuity risk for a user-owned project, although repository activity shows that the maintainer is currently active.

Project backing

The repository is owned by a user rather than an organization, so there is no organizational handoff evidence to offset the single-maintainer concentration.

Repo bus factor

One contributor made all 19 commits in the last three months, creating a high bus-factor risk and making continuity dependent on a single person.

Repo issue activity

There are no open issues or pull requests and no activity in the last month. This is not inherently negative for a small stable package, but it also gives limited evidence of community support.

Repo popularity

The repository has only 1 star, 0 forks, and 1 watcher. This does not establish abandonment by itself, but it provides little external adoption or community validation.