Package Health/live-controls/autoaddress

live-controls/autoaddress

This release is usable but carries meaningful maintenance and transparency risk. It has recent release and repository activity, is not deprecated or archived, uses a stable major version, has a matching repository with an organization owner, and includes a license file. However, all recent commits come from one contributor, the repository has no tests, changelog, security policy, or security scanning, and the project has no measurable stars or forks. The package is therefore reasonably active but should be adopted with normal safeguards and with awareness of its thin demonstrated maintainer base and limited verification tooling.

Latest v2.0.4

Packagist

68%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Package scaffolding

The artifact has a README, but it has no packaged tests or changelog, and the repository also has neither. The README includes unfinished content such as “TODO,” which weakens documentation and verification maturity.

Repo bus factor

All 4 commits in the last 3 months came from one contributor, creating a concentrated bus factor. Organization ownership provides some potential handoff capacity, but no second active contributor is demonstrated.

Repo commit activity

The repository recorded 4 commits in the last 3 months and has one active maintainer, showing recent work but only modest activity for a package developers may depend on.

Repo popularity

The repository has zero stars, forks, and watchers. Popularity is only supporting evidence, but the complete absence of visible adoption provides little external validation and modestly increases maturity uncertainty.

Repo tooling

Composer is used as a build tool, but no security scanning tools are configured. The build setup is appropriate for the package ecosystem, while the missing security tooling is a transparency and maintenance gap.