maarheeze/uuid-livewire

This is a healthy but young package with a clear MIT license, matching repository, tests, complete small file tree, stable non-prerelease versioning, and recent release and commit activity. The main concerns are that it is only 168 days old, has four releases, all recent commits come from one contributor, and the repository has no security policy or security-scanning tooling; zero stars and forks provide little external validation. The organization-owned repository provides some backing, but the absence of a second active contributor still leaves maintenance concentrated. Overall, it appears reasonable to depend on for its narrowly scoped Livewire integration, with normal diligence around its relatively short track record.

Latest 3.0.1

Packagist

78%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The package is young at 168 days with four releases, but all four were published within the last 12 months and the median release interval is about 8 days, showing active early development rather than abandonment. Its short history limits maturity evidence.

Repo bus factor

One contributor performed all three commits in the last three months, giving a 100% top-contributor share. Organization ownership provides some potential handoff capacity, but no second active contributor is shown, so concentration remains a maintenance risk.

Repo commit activity

There were three commits in the last three months, all from one active maintainer, indicating recent work but a limited observed maintenance base.

Repo issue activity

There are no open issues or pull requests and no recent issue or pull-request activity. This is not inherently negative for a small package, but it provides little evidence of community support or maintenance responsiveness.

Repo popularity

The repository has zero stars, forks, and watchers, so it has no demonstrated external adoption or community validation. This is a supporting concern rather than a decisive failure for a young, narrowly scoped package.