Public record
Software health reportschema 0.11.0 · metrics 2.10.0 · 2026-07-16 07:01 UTC

livewire / flux

The official Livewire UI component library

BladeNo license detected★ 956 stars⑂ 104 forkssince Sep 2024View on GitHub ↗
KindLibraryCommand-line toolhow this is determined

livewire/flux holds a health index of 69 out of 100, placing it in the Good band. It scores highest on Vitality (95/100) and lowest on AI Readiness (11/100). It was last updated today. 2 contributors account for most of its recent work.

69
overall / 100
Good

Software health index

Metrics are grouped into weighted categories on one standardized 1–100 scale. Overall starts as their weighted mean, calibrated against the distribution of the public record so bands carry percentile meaning; when public evidence triggers the High-Risk Jurisdiction Policy, the rating is adjusted and receives an At Risk ceiling of 34.

69
Exceptional93-100The record's top tier (≈ top 5%); essentially all checked criteria met
Excellent80-92Strong across the board; minor gaps
Good65-79Healthy; gaps are limited and manageable
Moderate50-64Acceptable with notable gaps; review recommended
Weak35-49Material weaknesses across several areas
At Risk20-34Significant weaknesses; adoption warrants caution
Critical1-19Severe problems (abandoned, single-maintainer, no hygiene)
VitalityCommunity &AdoptionSustainability &GovernanceEngineeringQualitySecurityAI Readiness

Score profile

Each axis is a category. The shape matters more than the average — a healthy subject fills the whole shape, while a spike-and-crater profile means strength in one dimension is masking risk in another.

The weighted overall 62 is calibrated to 69 on the published index scale (record calibration 2026-08-02).

Ownership

LivewireOrganization
984 followers19 public repossince Jun 2019

This repository is backed by an organization — shared, accountable stewardship that can outlive any single maintainer.

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
Packagistlivewire/fluxv2.15.01,007,3799427 days agouicomponentsfluxlaravellivewire

Metrics by category

Vitality

Is the project alive — is code being written and are releases shipping?

95Exceptional · 21% of overall
How it's scored
36/36Push recencylast push 0 days ago
27.7/36Commit cadence40/52 weeks with commits
18/18Commit volume280 commits in the last year
10/10OpenSSF Scorecard: Maintained24 commit(s) and 16 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year280
human_commit_share
days_since_last_push0
active_weeks_last_year40

Release discipline

100Exceptional
How it's scored
27/27Ships releases95 releases published
36/36Release recencylatest release 27 days ago
27/27Release cadencea release every ~16.4 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count95
latest_release_tagv2.15.0
releases_from_tagsno
days_since_latest_release27
mean_days_between_releases16.4
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: Signed-Releases. Remaining weights renormalized.

Community & Adoption

Does the project have users, downloads, attention, and a welcoming setup for contributors?

64Moderate · 17% of overall
How it's scored
48.3/60Stars956 stars
16.8/25Forks104 forks
7.5/15Watchers23 watchers
Inputs used
forks104
stars956
watchers23
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
0/22.5Licenseno license file detected
0/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
6.3/6.3PR template
Inputs used
has_readmeyes
has_licenseno
readme_badges
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_services
has_pull_request_templateyes
How it's scored
80/80Monthly downloads1,007,379 downloads/month across packagist
14/20Registry dependents125 packages depend on it
Inputs used
packageslivewire/flux
dependents125
ecosystemspackagist
total_downloads8,343,723
monthly_downloads1,007,379
unverified_packages_excluded

Sustainability & Governance

Will the project survive its people — bus factor, responsiveness, who backs it, and package upkeep?

82Excellent · 23% of overall
How it's scored
25.2/54Bus factor2 contributor(s) cover half of all commits
12.2/22.5Commit distributiontop contributor authored 46% of commits
13.5/13.5Contributor breadth33 contributors
10/10OpenSSF Scorecard: Contributorsproject has 4 contributing companies or organizations
Inputs used
bus_factor2
contributors_sampled33
top_contributor_share0.459
How it's scored
41.2/42Issue resolution98% of issues closed
23.3/30PR acceptance235/302 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
7.5/15OpenSSF Scorecard: Code-ReviewFound 12/24 approved changesets -- score normalized to 5
Inputs used
merged_prs235
open_issues27
closed_issues1,499
prs_merged_7d
prs_decided_7d
prs_merged_30d
prs_decided_30d
issue_closed_ratio0.982
closed_unmerged_prs67
first_time_authors_30d
first_time_prs_merged_30d
first_time_prs_decided_30d
Excluded from scoring (no data or not applicable): Newcomer PR acceptance. Remaining weights renormalized.
How it's scored
30/30Ownership backingorganization-owned
0/20Verified domainverified-domain status not read for this organization
21.5/25Owner reach984 followers of livewire
21.5/25Track record19 public repos, account ~7 yr old
Inputs used
followers984
owner_typeOrganization
is_verified
owner_loginlivewire
public_repos19
account_age_days2,584
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable1 package(s) on packagist
35/35Publish recencylatest publish 27 days ago
20/20Version history94 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packageslivewire/flux
ecosystemspackagist
any_deprecatedno
min_days_since_publish27

Engineering Quality

Are baseline engineering and documentation practices in place?

26At Risk · 19% of overall
How it's scored
0/24CI workflows
0/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
6.4/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Tests0 out of 18 merged PRs checked by a CI test -- score normalized to 0
Inputs used
has_cino
has_testsno
has_editorconfigyes
has_linter_configno
has_precommit_configno

Documentation

55Moderate
How it's scored
30/30README
0/25Documentation directory
15/15Documentation / homepage sitehttps://fluxui.dev
10/10Repository description
0/10Topics
0/10Wiki
Inputs used
topics
has_wikino
homepagehttps://fluxui.dev
docs_sitehttps://fluxui.dev
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

Are visible security and supply-chain practices strong, without unresolved high-risk jurisdiction exposure?

41Weak · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
0/7.5Branch-Protectionbranch protection not enabled on development/release branches
0/2.5CI-Tests0 out of 18 merged PRs checked by a CI test -- score normalized to 0
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
3.8/7.5Code-ReviewFound 12/24 approved changesets -- score normalized to 5
2.5/2.5Contributorsproject has 4 contributing companies or organizations
0/10Dangerous-Workflowno data
0/7.5Dependency-Update-Toolno update tool detected
0/5Fuzzingproject is not fuzzed
0/2.5Licenselicense file not detected
7.5/7.5Maintained24 commit(s) and 16 issue activity found in the last 90 days -- score normalized to 10
0/5Packagingno data
0/5Pinned-Dependenciesno data
0/5SASTSAST tool is not run on all commits -- score normalized to 0
0/5Security-Policysecurity policy file not detected
0/7.5Signed-Releasesno data
0/7.5Token-Permissionsno data
7.5/7.5Vulnerabilities0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated13
scorecard_versionv5.5.0
checks_inconclusive5
scorecard_aggregate4.1
Excluded from scoring (no data or not applicable): Dangerous-Workflow, Packaging, Pinned-Dependencies, Signed-Releases, Token-Permissions. Remaining weights renormalized.

AI Readiness

How well is the repo equipped to be developed and maintained with AI coding agents? Carries a deliberately small weight (4%): agent tooling is a real maintenance signal, but a repository with none can still reach 100/100.

11Critical · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
0/40Legible commit historyno data
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share
agent_instruction_files
agent_instruction_max_bytes
Excluded from scoring (no data or not applicable): Legible commit history. Remaining weights renormalized.
How it's scored
0/18One-command bootstrap
0/22Automated tests
0/11Lint / format config
0/11Static type checking
0/10Reproducible environment
0/10Demonstrated agent practiceno data
0/8Automated maintenanceno data
0/10OpenSSF Scorecard: Pinned-Dependenciesno data
Inputs used
has_nixno
has_testsno
lockfiles
has_dockerfileno
typed_languageno
bootstrap_files
has_devcontainerno
has_linter_configno
typecheck_configs
agent_commit_share
toolchain_manifests
dependency_bot_commit_share
Excluded from scoring (no data or not applicable): Demonstrated agent practice, Automated maintenance, OpenSSF Scorecard: Pinned-Dependencies. Remaining weights renormalized.
How it's scored
0/45Type-checkable codeBlade without a type-check config
55/55Manageable file sizes0/470 source files over 60KB
Inputs used
primary_languageBlade
largest_source_bytes18,128
source_files_sampled470
oversized_source_files0

Key facts

956GitHub stars
33contributors
280commits, last 12 months
0days since last push
95releases
2bus factor
27open issues
Packagistpackage ecosystems

More detail

OpenSSF Scorecard 4.1 / 10
4.1aggregate

Independent, tool-agnostic security assessment from the open-source OpenSSF Scorecard. Each check rewards a security practice, not a specific vendor's tool. Checks Scorecard could not determine are marked n/a and excluded from the security score (never counted as zero).Scorecard v5.5.0 · 2026-07-16 07:00 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
0CI-Tests0 out of 18 merged PRs checked by a CI test -- score normalized to 0
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
5Code-ReviewFound 12/24 approved changesets -- score normalized to 5
10Contributorsproject has 4 contributing companies or organizations
n/aDangerous-Workflowno workflows found
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
0Licenselicense file not detected
10Maintained24 commit(s) and 16 issue activity found in the last 90 days -- score normalized to 10
n/aPackagingpackaging workflow not detected
n/aPinned-Dependenciesno dependencies found
0SASTSAST tool is not run on all commits -- score normalized to 0
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
n/aToken-PermissionsNo tokens found
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 6
RegistryPackageVersion constraintManifest
Packagistilluminate/console^10.0|^11.0|^12.0|^13.0composer.json
Packagistilluminate/support^10.0|^11.0|^12.0|^13.0composer.json
Packagistilluminate/view^10.0|^11.0|^12.0|^13.0composer.json
Packagistsymfony/console^6.0|^7.0|^8.0composer.json
Packagistlivewire/livewire^3.7.4|^4.0composer.json
Packagistlaravel/prompts^0.1|^0.2|^0.3composer.json
All dependencies 7

Full resolved dependency set from the GitHub dependency graph: 6 direct and 1 indirect (transitive) packages. The transitive closure is complete when the repository commits a lockfile.

RegistryPackageVersionRelation
Packagistilluminate/consoledirect
Packagistilluminate/supportdirect
Packagistilluminate/viewdirect
Packagistlaravel/promptsdirect
Packagistlivewire/livewiredirect
Packagistsymfony/consoledirect
Packagistphpindirect
Raw JSON report machine-readable

Feedback

Spotted something off in this report, or have thoughts to share? Wrong measurements, missed tooling, ideas, questions — anything is welcome. Every message is read and gets a response.

The message is kept through sign-in.

Scores are signals, not warranties. They reflect publicly visible practices on GitHub — not a code audit, and not a security guarantee.

Missing data is excluded and weights renormalized, never scored as zero. Methodology is versioned and open: metrics v2.10.0, schema v0.11.0 — full methodology · metrics wiki.

How one result sits in the wider record: aggregate statisticsPackagist.