bluestarsystem/aura-ui

Aura UI appears healthy and actively maintained for this release: it has a clear MIT license, substantial package contents, tests and a changelog, a stable non-prerelease version, frequent recent releases, and a repository with 160 commits in the last 3 months. The repository is not archived, matches the package, and has two active contributors, although ownership and activity are concentrated, popularity is very low, and the repository lacks a security policy and consistently explicit workflow permissions. These are meaningful transparency and resilience gaps, but they do not outweigh the strong evidence of current maintenance and release discipline.

Latest v3.26.7

Packagist

82%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Maintainers

Only one registry account has publish access, which is a resilience concern for release continuity. This is partly mitigated by the repository's demonstrated activity, but registry publishing remains concentrated.

Project backing

The repository is owned by a user account rather than an organization, so there is no organization-level maintenance handoff signal to offset the concentrated ownership and contributor base.

Repo bus factor

Two contributors were active, but the leading contributor authored 61.875% of recent commits. The second contributor's substantial 38.125% share partly compensates for the concentration, leaving a modest resilience concern rather than a severe bus-factor risk.

Repo popularity

The repository has only 3 stars, 2 forks, and 0 watchers. Low popularity is supporting evidence rather than a verdict, but it provides little external adoption signal for a package with a relatively short history.

Repo tooling

Composer build tooling is present, but no security-scanning tools were detected. Build support is adequate while security-process transparency is limited.