smv7/smarty-asset-bundle

Usable with caveats: the repository is active, clearly matches the package, and the release is licensed and not deprecated. Adoption carries maintenance risk because the project is young, has one active contributor, no tests, and uses install-time scripts with write-enabled workflow permissions.

Latest v1.0.1

Packagist

58%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Lifecycle scripts

The package runs post-install and post-update Composer scripts, increasing installation complexity and the code executed during dependency operations. No provided signal shows these scripts are harmless or necessary.

Maintainers

Only one registry account has publishing access. This is not an administrative verdict, but it provides little redundancy for releasing fixes or responding to package issues.

Package scaffolding

A substantial README and GitHub Releases are present, but neither the package nor repository contains tests or a changelog. For an asset-processing package, the absence of tests is a real maintenance and regression concern.

Project backing

The repository is owned by an individual user rather than an organization, so the single-maintainer and single-contributor concentration is not offset by visible organizational backing.

Release history

The package is only 233 days old with three releases and two releases in the last 12 months, so its long-term maintenance record is still limited despite recent publishing activity.