Package Health/innopanda/laravel-asset-manager

innopanda/laravel-asset-manager

This release appears usable but is still very young: it has 15 releases across 22 days, active recent commits, tests, a changelog, and a substantial package tree, which support ongoing development and reasonable transparency. However, maintenance is concentrated entirely in one contributor, the repository has minimal adoption, and no security policy or security scanning is present. The linked repository name differs from the package name, although the README does mention the package, reducing concern about repository misassociation. Overall, this is a promising but immature dependency that should be adopted with normal version pinning and monitoring rather than treated as a mature, low-risk foundation.

Latest v1.0.14

Packagist

67%

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 concern for an independently owned package, although repository activity shows that the same maintainer is currently active.

Project backing

The repository owner is an individual user rather than an organization, so there is no organizational maintenance buffer to compensate for the concentrated contributor base.

Release history

The package is only 22 days old but already has 15 releases, with a median interval of about 1 hour 10 minutes; this shows active iteration but provides little evidence of long-term maintenance or release stability.

Repo bus factor

All 18 recent commits came from one contributor, giving the project a single-person bus factor and increasing abandonment or response-time risk if that contributor becomes unavailable.

Repo popularity

The repository has only 1 star, 0 forks, and 0 watchers. Popularity is supporting evidence rather than a verdict, but these figures provide little external validation or resilience evidence for a package intended for production use.