Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-10 13:50 UTC

aliyun / aliyun-cli

Alibaba Cloud CLI

GoApache-2.0★ 1,101 stars⑂ 235 forkssince Jun 2015View on GitHub ↗
KindLibraryCommand-line toolhow this is determined

aliyun/aliyun-cli holds a health index of 90 out of 100, placing it in the Excellent band. It scores highest on Vitality (91/100) and lowest on Community & Adoption (65/100). It was last updated today. 2 contributors account for most of its recent work.

90
overall / 100
Excellent

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.

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

Ownership

Alibaba CloudOrganization · verified domain
1,953 followers696 public repossince Jul 2011

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
Gogithub.com/aliyun/aliyun-cli/v3v3.5.0-3653 days ago

Metrics by category

Vitality

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

91Excellent · 21% of overall
How it's scored
36/36Push recency — last push 0 days ago
27.7/36Commit cadence — 40/52 weeks with commits
18/18Commit volume — 159 commits in the last year
10/10OpenSSF Scorecard: Maintained — 30 commit(s) and 2 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year159
human_commit_share1
days_since_last_push0
active_weeks_last_year40
How it's scored
27/27Ships releases — 100 releases published
36/36Release recency — latest release 3 days ago
27/27Release cadence — a release every ~7.5 days
0/10OpenSSF Scorecard: Signed-Releases — Project has not signed or included provenance with any releases.
Inputs used
releases_count100
latest_release_tagv3.5.0
releases_from_tagsno
days_since_latest_release3
mean_days_between_releases7.5

Community & Adoption

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

65Good · 17% of overall
How it's scored
49.3/60Stars — 1,101 stars
19.7/25Forks — 235 forks
9.1/15Watchers — 44 watchers
Inputs used
forks235
stars1,101
watchers44
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_badges3
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_servicesgithub.com, shields.io
has_pull_request_templateno

Sustainability & Governance

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

80Excellent · 23% of overall
How it's scored
25.2/54Bus factor — 2 contributor(s) cover half of all commits
15.2/22.5Commit distribution — top contributor authored 32% of commits
13.5/13.5Contributor breadth — 52 contributors
10/10OpenSSF Scorecard: Contributors — project has 6 contributing companies or organizations
Inputs used
bus_factor2
contributors_sampled52
top_contributor_share0.324
How it's scored
36.8/42Issue resolution — 88% of issues closed
15.3/30PR acceptance — 579/1,132 decided PRs merged
4.3/13Newcomer PR acceptance — 1/3 first-time contributors' PRs merged in 30d
9/15OpenSSF Scorecard: Code-Review — Found 19/29 approved changesets -- score normalized to 6
Inputs used
merged_prs579
open_issues36
closed_issues251
prs_merged_7d7
prs_decided_7d9
prs_merged_30d23
prs_decided_30d30
issue_closed_ratio0.875
closed_unmerged_prs553
first_time_authors_30d2
first_time_prs_merged_30d1
first_time_prs_decided_30d3
How it's scored
30/30Ownership backing — organization-owned
20/20Verified domain
23.7/25Owner reach — 1,953 followers of aliyun
25/25Track record — 696 public repos, account ~15 yr old
Inputs used
followers1,953
owner_typeOrganization
is_verifiedyes
owner_loginaliyun
public_repos696
account_age_days5,524

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 1 package(s) on go
35/35Publish recency — latest publish 3 days ago
20/20Version history — 365 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesgithub.com/aliyun/aliyun-cli/v3
ecosystemsgo
any_deprecatedno
min_days_since_publish3

Engineering Quality

Are baseline engineering and documentation practices in place?

77Good · 19% of overall
How it's scored
24/24CI workflows — 4 workflow(s)
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests — 23 out of 23 merged PRs checked by a CI test -- score normalized to 10
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configno
has_precommit_configno

Documentation

90Excellent
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage site — https://help.aliyun.com/zh/cli/
10/10Repository description
10/10Topics — 11 topics
0/10Wiki
Inputs used
topicsalibaba, alibabacloud, alibaba-cloud-cli, cloud-api, cli, alibaba-cloud-openapi, rpc-api, sdk, client, aliyun, openapi
has_wikino
homepagehttps://help.aliyun.com/zh/cli/
docs_sitehttps://help.aliyun.com/zh/cli/
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

66Good · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
0/7.5Branch-Protection — no data
2.5/2.5CI-Tests — 23 out of 23 merged PRs checked by a CI test -- score normalized to 10
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
4.5/7.5Code-Review — Found 19/29 approved changesets -- score normalized to 6
2.5/2.5Contributors — project has 6 contributing companies or organizations
10/10Dangerous-Workflow — no dangerous workflow patterns detected
7.5/7.5Dependency-Update-Tool — update tool detected
0/5Fuzzing — project is not fuzzed
2.5/2.5License — license file detected
7.5/7.5Maintained — 30 commit(s) and 2 issue activity found in the last 90 days -- score normalized to 10
0/5Packaging — no data
0/5Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
5/5SAST — SAST tool is run on all commits
5/5Security-Policy — security policy file detected
0/7.5Signed-Releases — Project has not signed or included provenance with any releases.
0/7.5Token-Permissions — detected GitHub workflow tokens with excessive permissions
2.2/7.5Vulnerabilities — 7 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate6.1
Excluded from scoring (no data or not applicable): Branch-Protection, Packaging. Remaining weights renormalized.
How it's scored
23.1/35Direct dependencies free of known advisories — 3 affected: github.com/klauspost/compress v1.17.8 (unknown), golang.org/x/crypto v0.54.0 (unknown), golang.org/x/mod v0.17.0 (unknown)
0/25Indirect dependencies free of known advisories — transitive set not separable from development and test dependencies in this scope
40/40No advisories left outstanding — no advisory has been public longer than 90 days
Inputs used
sourceosv
advisories7
affected_packages3
assessed_packages49
unassessed_packages0
affected_by_severityunknown 3
direct_affected_packages3
Excluded from scoring (no data or not applicable): Indirect dependencies free of known advisories. Remaining weights renormalized. Matched 49 resolved dependencies against OSV. This repository publishes no package the index resolves, so the repository dependency graph was assessed instead. That graph mixes development and test pins with shipped dependencies, so only the declared runtime dependencies are scored; transitive findings are reported as context and excluded from the score. 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.

68Good · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
15/15Machine-readable docs (llms.txt) — llms.txt served by the project website (https://help.aliyun.com/llms.txt)
35.2/40Legible commit history — 66 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtyes
llms_txt_urlhttps://help.aliyun.com/llms.txt
legible_history_share0.66
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
18/18One-command bootstrap — Makefile
22/22Automated tests
0/11Lint / format config
11/11Static type checking — Go (statically typed)
10/10Reproducible environment — lockfile
6/10Demonstrated agent practice — 3 of the last 100 commits agent-authored or agent-credited
5/8Automated maintenance — dependency automation configured, none observed in the sampled commits
0/10OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsyes
lockfilesgo.sum
has_dockerfileno
typed_languageyes
bootstrap_filesMakefile
has_devcontainerno
has_linter_configno
typecheck_configs—
agent_commit_share0.03
toolchain_manifestsaliyun-openapi-runtime/go.mod, go.mod
dependency_bot_commit_share0
How it's scored
45/45Type-checkable code — Go (statically typed)
53.7/55Manageable file sizes — 14/598 source files over 60KB
Inputs used
primary_languageGo
largest_source_bytes225,008
source_files_sampled598
oversized_source_files14
How it's scored
40/40API schema (OpenAPI/GraphQL/proto) — sls/logs.proto
20/20MCP server
0/40Runnable examples
Inputs used
example_dirs—
has_mcp_signalyes
api_schema_filessls/logs.proto
interfaces_expected_of—

Key facts

1,101GitHub stars
52contributors
159commits, last 12 months
0days since last push
100releases
2bus factor
36open issues
Gopackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • Could not fetch go package 'github.com/aliyun/aliyun-openapi-runtime' from its registry

More detail

Star and fork history 0 ★ / 235 ⇿
0Stars
235Forks
99Releases

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.

04080120160200240230232015-072021-022026-09
Major 0Minor 4Patch 95

Each point covers 11 days.

OpenSSF Scorecard 6.1 / 10
6.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-09-10 13:49 UTC

10Binary-Artifactsno binaries found in the repo
n/aBranch-Protectioninternal error: error during branchesHandler.setup: internal error: some github tokens can't read classic branch protection rules: https://github.com/ossf/scorecard-action/blob/main/docs/authentication/fine-grained-auth-token.md
10CI-Tests23 out of 23 merged PRs checked by a CI test -- score normalized to 10
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
6Code-ReviewFound 19/29 approved changesets -- score normalized to 6
10Contributorsproject has 6 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained30 commit(s) and 2 issue activity found in the last 90 days -- score normalized to 10
n/aPackagingpackaging workflow not detected
0Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
10SASTSAST tool is run on all commits
10Security-Policysecurity policy file detected
0Signed-ReleasesProject has not signed or included provenance with any releases.
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
3Vulnerabilities7 existing vulnerabilities detected
Direct dependencies 27
RegistryPackageVersion constraintManifest
Gogithub.com/alibabacloud-go/darabonba-openapi/v2v2.2.4aliyun-openapi-runtime/go.mod
Gogithub.com/alibabacloud-go/teav1.5.2aliyun-openapi-runtime/go.mod
Gogithub.com/aliyun/credentials-gov1.4.7aliyun-openapi-runtime/go.mod
Gogithub.com/jmespath/go-jmespathv0.4.0aliyun-openapi-runtime/go.mod
Gogolang.org/x/termv0.45.0aliyun-openapi-runtime/go.mod
Gogoogle.golang.org/protobufv1.36.11aliyun-openapi-runtime/go.mod
Gogithub.com/alibabacloud-go/alibabacloud-gateway-slsv0.3.0go.mod
Gogithub.com/alibabacloud-go/darabonba-openapi/v2v2.2.4go.mod
Gogithub.com/alibabacloud-go/teav1.5.2go.mod
Gogithub.com/alibabacloud-go/tea-utils/v2v2.0.9go.mod
Gogithub.com/aliyun/alibaba-cloud-sdk-gov1.63.107go.mod
Gogithub.com/aliyun/aliyun-openapi-runtimev0.0.0-00010101000000-000000000000go.mod
Gogithub.com/aliyun/aliyun-oss-go-sdkv3.0.2+incompatiblego.mod
Gogithub.com/aliyun/credentials-gov1.4.7go.mod
Gogithub.com/alyu/configparserv0.0.0-20191103060215-744e9a66e7bcgo.mod
Gogithub.com/droundy/gooptv0.0.0-20220217183150-48d6390ad4d1go.mod
Gogithub.com/gogo/protobufv1.3.2go.mod
Gogithub.com/jmespath/go-jmespathv0.4.0go.mod
Gogithub.com/klauspost/compressv1.17.8go.mod
Gogithub.com/pierrec/lz4v2.6.1+incompatiblego.mod
Gogithub.com/stretchr/testifyv1.10.0go.mod
Gogithub.com/syndtr/goleveldbv1.0.0go.mod
Gogolang.org/x/cryptov0.54.0go.mod
Gogolang.org/x/modv0.17.0go.mod
Gogolang.org/x/termv0.45.0go.mod
Gogopkg.in/check.v1v1.0.0-20201130134442-10cb98267c6cgo.mod
Gogopkg.in/ini.v1v1.67.0go.mod
All dependencies 49

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

RegistryPackageVersionRelation
Gogithub.com/alibabacloud-go/alibabacloud-gateway-slsv0.3.0direct
Gogithub.com/alibabacloud-go/darabonba-openapi/v2v2.2.4direct
Gogithub.com/alibabacloud-go/teav1.5.2direct
Gogithub.com/alibabacloud-go/tea-utils/v2v2.0.9direct
Gogithub.com/aliyun/alibaba-cloud-sdk-gov1.63.107direct
Gogithub.com/aliyun/aliyun-oss-go-sdkv3.0.2+incompatibledirect
Gogithub.com/aliyun/credentials-gov1.4.7direct
Gogithub.com/alyu/configparserv0.0.0-20191103060215-744e9a66e7bcdirect
Gogithub.com/droundy/gooptv0.0.0-20220217183150-48d6390ad4d1direct
Gogithub.com/gogo/protobufv1.3.2direct
Gogithub.com/klauspost/compressv1.17.8direct
Gogithub.com/pierrec/lz4v2.6.1+incompatibledirect
Gogithub.com/stretchr/testifyv1.10.0direct
Gogithub.com/syndtr/goleveldbv1.0.0direct
Gogolang.org/x/cryptov0.54.0direct
Gogolang.org/x/modv0.17.0direct
Gogolang.org/x/termv0.45.0direct
Gogoogle.golang.org/protobufv1.36.11direct
Gogopkg.in/check.v1v1.0.0-20201130134442-10cb98267c6cdirect
Gogopkg.in/ini.v1v1.67.0direct
Gogithub.com/alibabacloud-go/alibabacloud-gateway-sls-utilv0.3.0indirect
Gogithub.com/alibabacloud-go/alibabacloud-gateway-spiv0.0.5indirect
Gogithub.com/alibabacloud-go/darabonba-arrayv0.1.0indirect
Gogithub.com/alibabacloud-go/darabonba-encode-utilv0.0.2indirect
Gogithub.com/alibabacloud-go/darabonba-mapv0.0.2indirect
Gogithub.com/alibabacloud-go/darabonba-signature-utilv0.0.7indirect
Gogithub.com/alibabacloud-go/darabonba-stringv1.0.2indirect
Gogithub.com/alibabacloud-go/debugv1.0.1indirect
Gogithub.com/alibabacloud-go/openapi-utilv0.1.0indirect
Gogithub.com/alibabacloud-go/tea-utilsv1.3.1indirect
Gogithub.com/clbanning/mxj/v2v2.7.0indirect
Gogithub.com/davecgh/go-spewv1.1.1indirect
Gogithub.com/golang/snappyv1.0.0indirect
Gogithub.com/gorilla/websocketv1.5.3indirect
Gogithub.com/json-iterator/gov1.1.12indirect
Gogithub.com/kr/prettyv0.3.1indirect
Gogithub.com/kr/textv0.2.0indirect
Gogithub.com/modern-go/concurrentv0.0.0-20180306012644-bacd9c7ef1ddindirect
Gogithub.com/modern-go/reflect2v1.0.2indirect
Gogithub.com/onsi/ginkgov1.16.5indirect
Gogithub.com/onsi/gomegav1.30.0indirect
Gogithub.com/opentracing/opentracing-gov1.2.1-0.20220228012449-10b1cf09e00bindirect
Gogithub.com/pmezard/go-difflibv1.0.0indirect
Gogithub.com/rogpeppe/go-internalv1.12.0indirect
Gogithub.com/tjfoc/gmsmv1.4.1indirect
Gogolang.org/x/netv0.56.0indirect
Gogolang.org/x/sysv0.47.0indirect
Gogolang.org/x/timev0.11.0indirect
Gogopkg.in/yaml.v3v3.0.1indirect
Dependency advisories 3

This repository publishes no package the index resolves, so its own dependency graph was assessed — 49 packages, which also include development and test pins that never ship: 3 carry known advisories, of which 3 are direct.

PackageVersionRelationSeverityAdvisoriesFixed in
github.com/klauspost/compressv1.17.8directunknown11.18.7
golang.org/x/cryptov0.54.0directunknown40.56.0
golang.org/x/modv0.17.0directunknown21.27.0-rc.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 — Go.