Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-16 15:31 UTC

Semantic-Org / Semantic-UI

Semantic is a UI component framework based around useful principles from natural language.

JavaScript · LessMIT★ 51,018 stars⑂ 4,847 forkssince Apr 2013View on GitHub ↗

Semantic-Org/Semantic-UI holds a health index of 27 out of 100, placing it in the At Risk band. It scores highest on Community & Adoption (84/100) and lowest on Vitality (18/100). It was last updated 657 days ago. A single contributor accounts for most of its recent work.

27
overall / 100
At Risk

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.

27
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 47 is calibrated to 45 on the published index scale (record calibration 2026-08-02).

Ownership

Semantic OrgOrganization
241 followers81 public repossince Oct 2013

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
npmsemantic-ui2.5.015,344841440 days ago—
Packagistsemantic/ui2.5.089611440 days agoframeworkuicsssemantic

Metrics by category

Vitality

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

18Critical · 21% of overall
How it's scored
0/36Push recency — last push 657 days ago
0/36Commit cadence — 0/52 weeks with commits
0/18Commit volume — 0 commits in the last year
0/10OpenSSF Scorecard: Maintained — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Inputs used
commits_last_year0
human_commit_share1
days_since_last_push657
active_weeks_last_year0
How it's scored
27/27Ships releases — 100 releases published
0/36Release recency — latest release 1,440 days ago
12.6/27Release cadence — a release every ~209.6 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count100
latest_release_tag2.5.0
releases_from_tagsno
days_since_latest_release1,440
mean_days_between_releases209.6
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?

84Excellent · 17% of overall

Popularity & adoption

100Exceptional
How it's scored
60/60Stars — 51,018 stars
25/25Forks — 4,847 forks
15/15Watchers — 1,274 watchers
Inputs used
forks4,847
stars51,018
watchers1,274
growth_stateorganic
growth_factor_pct100

Community health

85Excellent
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (MIT)
18/18CONTRIBUTING guide
0/13.5Code of conduct
7.2/7.2Issue template
6.3/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges1
has_contributingyes
has_issue_templateyes
has_code_of_conductno
readme_badge_servicesshields.io
has_pull_request_templateyes
How it's scored
55.8/80Monthly downloads — 15,433 downloads/month across npm, packagist
2/20Registry dependents — 1 packages depend on it
Inputs used
packagessemantic-ui, semantic/ui
dependents1
ecosystemsnpm, packagist
total_downloads36,204
monthly_downloads15,433
unverified_packages_excluded—

Sustainability & Governance

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

57Moderate · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
3/22.5Commit distribution — top contributor authored 87% of commits
13.5/13.5Contributor breadth — 100 contributors
10/10OpenSSF Scorecard: Contributors — project has 22 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled100
top_contributor_share0.868
How it's scored
35.5/42Issue resolution — 84% of issues closed
13.8/30PR acceptance — 356/776 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
1.5/15OpenSSF Scorecard: Code-Review — Found 5/28 approved changesets -- score normalized to 1
Inputs used
merged_prs356
open_issues964
closed_issues5,269
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio0.845
closed_unmerged_prs420
first_time_authors_30d0
first_time_prs_merged_30d0
first_time_prs_decided_30d0
Excluded from scoring (no data or not applicable): Newcomer PR acceptance. Remaining weights renormalized.
How it's scored
30/30Ownership backing — organization-owned
0/20Verified domain
17.1/25Owner reach — 241 followers of Semantic-Org
25/25Track record — 81 public repos, account ~12 yr old
Inputs used
followers241
owner_typeOrganization
is_verifiedno
owner_loginSemantic-Org
public_repos81
account_age_days4,705
How it's scored
25/25Published & resolvable — 2 package(s) on npm, packagist
4/35Publish recency — latest publish 1,440 days ago
20/20Version history — 84 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagessemantic-ui, semantic/ui
ecosystemsnpm, packagist
any_deprecatedno
min_days_since_publish1,440

Engineering Quality

Are baseline engineering and documentation practices in place?

44Weak · 19% of overall
How it's scored
0/24CI workflows
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Tests — 0 out of 5 merged PRs checked by a CI test -- score normalized to 0
Inputs used
has_cino
has_testsyes
has_editorconfigno
has_linter_configno
has_precommit_configno
How it's scored
30/30README
0/25Documentation directory
15/15Documentation / homepage site — http://www.semantic-ui.com
10/10Repository description
10/10Topics — 10 topics
10/10Wiki
Inputs used
topicsui, ui-components, flexbox, css-framework, dropdown, button, popup, sidebar, tooltip, semantic
has_wikiyes
homepagehttp://www.semantic-ui.com
docs_sitehttp://www.semantic-ui.com
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

36Weak · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
0/7.5Branch-Protection — branch protection not enabled on development/release branches
0/2.5CI-Tests — 0 out of 5 merged PRs checked by a CI test -- score normalized to 0
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
0.8/7.5Code-Review — Found 5/28 approved changesets -- score normalized to 1
2.5/2.5Contributors — project has 22 contributing companies or organizations
0/10Dangerous-Workflow — no data
0/7.5Dependency-Update-Tool — no update tool detected
0/5Fuzzing — project is not fuzzed
2.5/2.5License — license file detected
0/7.5Maintained — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
0/5Packaging — no data
0/5Pinned-Dependencies — no data
0/5SAST — SAST tool is not run on all commits -- score normalized to 0
0/5Security-Policy — security policy file not detected
0/7.5Signed-Releases — no data
0/7.5Token-Permissions — no data
7.5/7.5Vulnerabilities — 0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated13
scorecard_versionv5.5.0
checks_inconclusive5
scorecard_aggregate3
Excluded from scoring (no data or not applicable): Dangerous-Workflow, Packaging, Pinned-Dependencies, Signed-Releases, Token-Permissions. Remaining weights renormalized.
How it's scored
35/35Direct dependencies free of known advisories — no direct dependency carries a known advisory
5.3/25Indirect dependencies free of known advisories — 6 affected: decode-uri-component 0.2.2 (high 7.5), lodash.template 3.6.2 (high 7.2), tmp 0.0.33 (high 7.5), +3 more
21.3/40No advisories left outstanding — 5 advisory-carrying package(s) unaddressed past 90 days; oldest published 2,651 days ago
Inputs used
sourceosv
advisories8
affected_packages6
assessed_packages469
unassessed_packages0
affected_by_severityhigh 5, moderate 1
direct_affected_packages0
Matched the npm:semantic-ui@2.5.0 runtime dependency closure — what installing the published package pulls in — 469 packages. Reachability is not analyzed.

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.

36Weak · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
10.1/40Legible commit history — 19 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.19
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
0/18One-command bootstrap
22/22Automated tests
0/11Lint / format config
0/11Static type checking
0/10Reproducible environment
0/10Demonstrated agent practice — no agent-authored commits among the last 100
0/8Automated maintenance — no automated dependency updates observed
0/10OpenSSF Scorecard: Pinned-Dependencies — no data
Inputs used
has_nixno
has_testsyes
lockfiles—
has_dockerfileno
typed_languageno
bootstrap_files—
has_devcontainerno
has_linter_configno
typecheck_configs—
agent_commit_share0
toolchain_manifests—
dependency_bot_commit_share0
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: Pinned-Dependencies. Remaining weights renormalized.
How it's scored
0/45Type-checkable code — JavaScript without a type-check config
53/55Manageable file sizes — 3/84 source files over 60KB
Inputs used
primary_languageJavaScript
largest_source_bytes149,285
source_files_sampled84
oversized_source_files3
How it's scored
0/40API schema (OpenAPI/GraphQL/proto) — not applicable to this kind of software
0/20MCP server — not applicable to this kind of software
40/40Runnable examples — examples
Inputs used
example_dirsexamples
has_mcp_signalno
api_schema_files—
interfaces_expected_of—
Excluded from scoring (no data or not applicable): API schema (OpenAPI/GraphQL/proto), MCP server. Remaining weights renormalized.

Key facts

51,018GitHub stars
100contributors
0commits, last 12 months
657days since last push
100releases
1bus factor
964open issues
npm, Packagistpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • Star history carried forward from 2026-07-21: GitHub restricted the stargazers API to repository admins, so it can no longer be collected. The repository has 51018 stars today.

More detail

Star and fork history 51,046 ★ / 4,847 ⇿
51,046Stars
4,847Forks
1Releases

When each star and fork was added, collected from GitHub and bucketed by day. Cumulative growth sits directly above the daily additions it is made of, so the two read against each other: steady organic accretion looks nothing like an abrupt, short-lived burst. Where that difference is measurable, it is reported as growth authenticity.

Only the most recent history is shown — this repository exceeds the collection window, so the earliest history is not captured.

Star history is shown as collected on 2026-07-21. GitHub restricted the stargazers API to repository administrators in July 2026, so this series can no longer be extended; the current star total above remains live.

010,00020,00030,00040,00050,00060,00051,0464,847212019-022022-112026-08
Major 0Minor 1Patch 0

Each point covers 7 days.

OpenSSF Scorecard 3.0 / 10
3.0aggregate

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-09-16 15:30 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
0CI-Tests0 out of 5 merged PRs checked by a CI test -- score normalized to 0
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
1Code-ReviewFound 5/28 approved changesets -- score normalized to 1
10Contributorsproject has 22 contributing companies or organizations
n/aDangerous-Workflowno workflows found
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
0Maintained0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
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 33
RegistryPackageVersion constraintManifest
npmbetter-console*package.json
npmdel*package.json
npmextend*package.json
npmgulp*package.json
npmgulp-autoprefixer*package.json
npmgulp-chmod*package.json
npmgulp-clean-css*package.json
npmgulp-clone*package.json
npmgulp-concat*package.json
npmgulp-concat-css*package.json
npmgulp-copy*package.json
npmgulp-dedupe*package.json
npmgulp-flatten*package.json
npmgulp-header*package.json
npmgulp-if*package.json
npmgulp-json-editor^2.5.4package.json
npmgulp-less*package.json
npmgulp-notify*package.json
npmgulp-plumber*package.json
npmgulp-print*package.json
npmgulp-rename*package.json
npmgulp-replace*package.json
npmgulp-rtlcss*package.json
npmgulp-uglify*package.json
npmjquery^3.5.1package.json
npmmap-stream*package.json
npmmerge-stream^1.0.0package.json
npmmkdirp^1.0.4package.json
npmprompt-sui^3.2.1package.json
npmreplace-ext*package.json
npmrequire-dot-file*package.json
npmwrench-sui^0.0.3package.json
npmyamljs*package.json
All dependencies 40

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

RegistryPackageVersionRelation
npmbetter-console*direct
npmdel*direct
npmextend*direct
npmgulp*direct
npmgulp-autoprefixer*direct
npmgulp-chmod*direct
npmgulp-clean-css*direct
npmgulp-clone*direct
npmgulp-concat*direct
npmgulp-concat-css*direct
npmgulp-copy*direct
npmgulp-dedupe*direct
npmgulp-flatten*direct
npmgulp-header*direct
npmgulp-if*direct
npmgulp-json-editor^2.5.4direct
npmgulp-less*direct
npmgulp-notify*direct
npmgulp-plumber*direct
npmgulp-print*direct
npmgulp-rename*direct
npmgulp-replace*direct
npmgulp-rtlcss*direct
npmgulp-uglify*direct
npmjquery^3.5.1direct
npmmap-stream*direct
npmmerge-stream*direct
npmmerge-stream^1.0.0direct
npmmkdirp^1.0.4direct
npmprompt-sui^3.2.1direct
npmreplace-ext*direct
npmrequire-dot-file*direct
npmwrench-sui^0.0.3direct
npmyamljs*direct
npm@jsdevtools/npm-publish^1.4.3indirect
npm@octokit/rest^19.0.4indirect
npmgulp-concat-filenames*indirect
npmgulp-debug^4.0.0indirect
npmgulp-git^2.10.1indirect
npmgulp-tap^2.0.0indirect
Dependency advisories 6

Installing npm:semantic-ui@2.5.0 pulls in 469 packages, direct and transitive: 6 carry known advisories, of which 0 are direct dependencies.

PackageVersionRelationSeverityAdvisoriesFixed in
decode-uri-component0.2.2indirecthigh10.5.0
lodash.template3.6.2indirecthigh14.17.21
tmp0.0.33indirecthigh20.2.6
url-regex3.2.0indirecthigh1—
uuid8.3.2indirecthigh113.0.1
diff1.0.8indirectmoderate28.0.3

An advisory means the version recorded in the dependency graph falls inside an advisory’s affected range. Reachability is not analysed, and the graph includes development and test pins — a finding may concern tooling rather than shipped software.

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.34.0 — full methodology · metrics wiki.

How one result sits in the wider record: aggregate statistics — npm, Packagist.