Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-10-17 13:38 UTC

webos-tools / cli

command-line interface (CLI) for webOS

HTML · JavaScriptApache-2.0★ 96 stars⑂ 30 forkssince Mar 2024View on GitHub ↗
KindLibraryCommand-line toolNetwork servicehow this is determined

webos-tools/cli holds a health index of 53 out of 100, placing it in the Moderate band. It scores highest on Vitality (64/100) and lowest on Security (33/100). It was last updated 39 days ago. 2 contributors account for most of its recent work.

53
overall / 100
Moderate

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.

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

Ownership

webOS SDK ToolsOrganization
26 followers2 public repossince Mar 2024

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
npm@webos-tools/cli3.2.648,4081839 days agoares-cliweboswebos-osewebos-tvwebos-cliwebos-sdklg

Metrics by category

Vitality

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

64Moderate · 21% of overall
How it's scored
18/36Push recency — last push 39 days ago
7.6/36Commit cadence — 11/52 weeks with commits
13.4/18Commit volume — 30 commits in the last year
7/10OpenSSF Scorecard: Maintained — 9 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 7
Inputs used
commits_last_year30
human_commit_share1
days_since_last_push39
active_weeks_last_year11
How it's scored
27/27Ships releases — 16 releases published
36/36Release recency — latest release 39 days ago
19.8/27Release cadence — a release every ~87.2 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count16
latest_release_tagv3.2.6
releases_from_tagsno
days_since_latest_release39
mean_days_between_releases87.2
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?

57Moderate · 17% of overall
How it's scored
32.1/60Stars — 96 stars
12.2/25Forks — 30 forks
5.3/15Watchers — 10 watchers
Inputs used
forks30
stars96
watchers10
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (Apache-2.0)
0/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges0
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_services—
has_pull_request_templateno
How it's scored
62.5/80Monthly downloads — 48,408 downloads/month across npm
0/20Registry dependents — not reported by this ecosystem
Inputs used
packages@webos-tools/cli
dependents—
ecosystemsnpm
total_downloads—
monthly_downloads48,408
unverified_packages_excluded—
Excluded from scoring (no data or not applicable): Registry dependents. Remaining weights renormalized.

Sustainability & Governance

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

61Moderate · 23% of overall
How it's scored
25.2/54Bus factor — 2 contributor(s) cover half of all commits
11.9/22.5Commit distribution — top contributor authored 47% of commits
13.5/13.5Contributor breadth — 12 contributors
3/10OpenSSF Scorecard: Contributors — project has 1 contributing companies or organizations -- score normalized to 3
Inputs used
bus_factor2
contributors_sampled12
top_contributor_share0.47
How it's scored
17.3/42Issue resolution — 41% of issues closed
23.6/30PR acceptance — 22/28 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
1.5/15OpenSSF Scorecard: Code-Review — Found 2/18 approved changesets -- score normalized to 1
Inputs used
merged_prs22
open_issues10
closed_issues7
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio0.412
closed_unmerged_prs6
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
10.3/25Owner reach — 26 followers of webos-tools
8.7/25Track record — 2 public repos, account ~2 yr old
Inputs used
followers26
owner_typeOrganization
is_verifiedno
owner_loginwebos-tools
public_repos2
account_age_days957

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 1 package(s) on npm
35/35Publish recency — latest publish 39 days ago
20/20Version history — 18 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packages@webos-tools/cli
ecosystemsnpm
any_deprecatedno
min_days_since_publish39

Engineering Quality

Are baseline engineering and documentation practices in place?

44Weak · 19% of overall
How it's scored
0/24CI workflows
24/24Tests present
16/16Linter config — .eslintrc.js
0/9.6Pre-commit hooks
0/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Tests — 0 out of 7 merged PRs checked by a CI test -- score normalized to 0
Inputs used
has_cino
has_testsyes
has_editorconfigno
has_linter_configyes
has_precommit_configno

Documentation

50Moderate
How it's scored
30/30README
0/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
0/10Topics
10/10Wiki
Inputs used
topics—
has_wikiyes
homepage—
docs_site—
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

33At Risk · 16% of overall
How it's scored
4.5/7.5Binary-Artifacts — binaries present in source code
2.2/7.5Branch-Protection — branch protection is not maximal on development and all release branches
0/2.5CI-Tests — 0 out of 7 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 2/18 approved changesets -- score normalized to 1
0.8/2.5Contributors — project has 1 contributing companies or organizations -- score normalized to 3
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
5.2/7.5Maintained — 9 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 7
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
0.8/7.5Vulnerabilities — 9 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated13
scorecard_versionv5.5.0
checks_inconclusive5
scorecard_aggregate2.4
Excluded from scoring (no data or not applicable): Dangerous-Workflow, Packaging, Pinned-Dependencies, Signed-Releases, Token-Permissions. Remaining weights renormalized.
How it's scored
20.2/35Direct dependencies free of known advisories — 1 affected: sprintf-js 1.1.3 (moderate 5.3)
10/25Indirect dependencies free of known advisories — 1 affected: braces 3.0.3 (high 7.5)
40/40No advisories left outstanding — no advisory has been public longer than 90 days
Inputs used
sourceosv
advisories2
affected_packages2
assessed_packages231
unassessed_packages0
affected_by_severityhigh 1, moderate 1
direct_affected_packages1
Matched the npm:@webos-tools/cli@3.2.6 runtime dependency closure — what installing the published package pulls in — 231 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)
27.2/40Legible commit history — 51 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.51
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format config — .eslintrc.js
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_configyes
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 — HTML without a type-check config
54.4/55Manageable file sizes — 7/661 source files over 60KB
Inputs used
primary_languageHTML
largest_source_bytes235,420
source_files_sampled661
oversized_source_files7

Key facts

96GitHub stars
12contributors
30commits, last 12 months
39days since last push
16releases
2bus factor
10open issues
npmpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token

More detail

Star and fork history 0 ★ / 30 ⇿
0Stars
30Forks
15Releases

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.

0510152025302932024-032025-062026-10
Major 0Minor 2Patch 13

Each point covers 3 days.

OpenSSF Scorecard 2.4 / 10
2.4aggregate

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-10-17 13:37 UTC

6Binary-Artifactsbinaries present in source code
3Branch-Protectionbranch protection is not maximal on development and all release branches
0CI-Tests0 out of 7 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 2/18 approved changesets -- score normalized to 1
3Contributorsproject has 1 contributing companies or organizations -- score normalized to 3
n/aDangerous-Workflowno workflows found
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
7Maintained9 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 7
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
1Vulnerabilities9 existing vulnerabilities detected
Direct dependencies 33
RegistryPackageVersion constraintManifest
npmar-async0.1.4package.json
npmasync3.2.6package.json
npmbluebird3.7.2package.json
npmbody-parser2.3.0package.json
npmchalk4.1.2package.json
npmchardet2.2.0package.json
npmchokidar4.0.3package.json
npmcombined-stream1.0.8package.json
npmcsv-writer1.6.0package.json
npmeasy-table1.2.0package.json
npmelfy1.0.0package.json
npmencoding0.1.13package.json
npmexpress5.2.1package.json
npmfs-extra11.3.6package.json
npmfstream1.0.12package.json
npminherits2.0.4package.json
npminquirer8.2.7package.json
npmjsonschema1.5.0package.json
npmmkdirp3.0.1package.json
npmnopt8.1.0package.json
npmnpmlog7.0.1package.json
npmora5.4.0package.json
npmrimraf6.1.3package.json
npmsemver7.7.4package.json
npmshelljs0.10.0package.json
npmsprintf-js1.1.3package.json
npmssdp-js1.0.1package.json
npmssh2^1.17.0package.json
npmstream-buffers3.0.3package.json
npmstrip-bom4.0.0package.json
npmtar^7.5.22package.json
npmtemp0.9.4package.json
npmterser5.48.0package.json
All dependencies 38

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

RegistryPackageVersionRelation
npmar-async0.1.4direct
npmasync3.2.6direct
npmbluebird3.7.2direct
npmbody-parser2.3.0direct
npmchalk4.1.2direct
npmchardet2.2.0direct
npmchokidar4.0.3direct
npmcombined-stream1.0.8direct
npmcsv-writer1.6.0direct
npmeasy-table1.2.0direct
npmelfy1.0.0direct
npmencoding0.1.13direct
npmexpress4.xdirect
npmexpress5.2.1direct
npmfs-extra11.3.6direct
npmfstream1.0.12direct
npminherits2.0.4direct
npminquirer8.2.7direct
npmjsonschema1.5.0direct
npmmkdirp3.0.1direct
npmnopt8.1.0direct
npmnpmlog7.0.1direct
npmora5.4.0direct
npmrimraf6.1.3direct
npmsemver7.7.4direct
npmshelljs0.10.0direct
npmsprintf-js1.1.3direct
npmssdp-js1.0.1direct
npmssh2^1.17.0direct
npmstream-buffers3.0.3direct
npmstrip-bom4.0.0direct
npmtar^7.5.22direct
npmtemp0.9.4direct
npmterser5.48.0direct
npmeslint8.57.1indirect
npmeslint-plugin-import2.32.0indirect
npmjasmine5.7.0indirect
npmjasmine-spec-reporter7.0.0indirect
Dependency advisories 2

Installing npm:@webos-tools/cli@3.2.6 pulls in 231 packages, direct and transitive: 2 carry known advisories, of which 1 are direct dependencies.

PackageVersionRelationSeverityAdvisoriesFixed in
braces3.0.3indirecthigh1—
sprintf-js1.1.3directmoderate1—

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.