Package Health/mediagone/vue-in-twig-bundle

mediagone/vue-in-twig-bundle

This is a young but actively maintained Composer package: it has 15 releases in 92 days, recent repository activity, a clear MIT license, a substantial README, a matching source repository, and no deprecation or install-time lifecycle scripts. Adoption carries moderate maintenance risk because all 26 recent commits come from one contributor, the artifact and repository contain no tests or changelog, the repository has no security policy or security scanning, and the package remains on an unstable 0.x major version. Overall it appears usable for dependency adoption, but consumers should expect a relatively immature project and consider pinning versions and monitoring maintenance.

Latest 0.4.10

Packagist

72%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Package scaffolding

A substantial README documents installation and usage, but neither the artifact nor repository contains tests or a changelog, leaving useful maintenance and regression-safety gaps for a young package.

Project backing

The linked repository is owned by an individual user, not an organization, so the concentrated maintainer activity cannot be discounted as normal organization-level ownership.

Repo bus factor

One contributor made all 26 commits in the last three months, creating a significant single-maintainer continuity risk; the repository owner is an individual user rather than an organization.

Repo popularity

The repository has zero stars, forks, and watchers. This is weak supporting evidence for maturity, but it is not by itself a decisive health problem for a young, specialized package.

Repo tooling

Composer is used as a build tool, but no security scanning tools are configured. The missing scanning reduces assurance but is not severe on its own for this package.