Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-16 02:50 UTC

modelstudioai / cli

Official Model Studio CLI(阿里云百炼 CLI)built for AI Agent frameworks, exposing models, search, multimodal, and workflow capabilities as structured tool calls.

TypeScriptApache-2.0★ 332 stars⑂ 28 forkssince May 2026View on GitHub ↗
KindCommand-line toolLibraryhow this is determined

modelstudioai/cli holds a health index of 83 out of 100, placing it in the Excellent band. It scores highest on Vitality (81/100) and lowest on Security (50/100). It was last updated today. 3 contributors account for most of its recent work.

83
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.

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

Ownership

Model Studio Organization
208 followers9 public repossince May 2026

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
npmbailian-cli1.25.017,5701691 day agoagentaiclimodel-studio
npmbailian-cli-core1.25.017,4201651 day ago—
npmknowledge-studio-cli1.19.02,6233113 days agoalibaba-cloudaliyunbailiandashscopeknowledge-basemodel-studioragretrieval
npmbailian-cli-runtime1.25.017,0491141 day ago—
npmbailian-cli-commands1.25.016,8471141 day ago—
npmbailian-kb-dsh0.1.19576322 days agoalibaba-cloudaliyunbailiandashscopedeepseek-harnessdshknowledge-baserag

Metrics by category

Vitality

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

81Excellent · 21% of overall
How it's scored
36/36Push recency — last push 0 days ago
11.1/36Commit cadence — 16/52 weeks with commits
18/18Commit volume — 881 commits in the last year
10/10OpenSSF Scorecard: Maintained — 30 commit(s) and 9 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year881
human_commit_share1
days_since_last_push0
active_weeks_last_year16
How it's scored
27/27Ships releases — 56 releases published
36/36Release recency — latest release 1 days ago
27/27Release cadence — a release every ~0.5 days
0/10OpenSSF Scorecard: Signed-Releases — Project has not signed or included provenance with any releases.
Inputs used
releases_count56
latest_release_tagv1.25.0
releases_from_tagsno
days_since_latest_release1
mean_days_between_releases0.5

Community & Adoption

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

66Good · 17% of overall
How it's scored
40.9/60Stars — 332 stars
11.9/25Forks — 28 forks
0/15Watchers — 1 watchers
Inputs used
forks28
stars332
watchers1
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)
18/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges4
has_contributingyes
has_issue_templateno
has_code_of_conductno
readme_badge_servicesshields.io
has_pull_request_templateno
How it's scored
64.8/80Monthly downloads — 72,085 downloads/month across npm
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagesbailian-cli, bailian-cli-core, knowledge-studio-cli, bailian-cli-runtime, bailian-cli-commands, bailian-kb-dsh
dependents—
ecosystemsnpm
total_downloads—
monthly_downloads72,085
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?

75Good · 23% of overall
How it's scored
36/54Bus factor — 3 contributor(s) cover half of all commits
15.3/22.5Commit distribution — top contributor authored 32% of commits
13.5/13.5Contributor breadth — 15 contributors
10/10OpenSSF Scorecard: Contributors — project has 5 contributing companies or organizations
Inputs used
bus_factor3
contributors_sampled15
top_contributor_share0.319
How it's scored
32/42Issue resolution — 76% of issues closed
24/30PR acceptance — 143/179 decided PRs merged
13/13Newcomer PR acceptance — 1/1 first-time contributors' PRs merged in 30d
7.5/15OpenSSF Scorecard: Code-Review — Found 4/8 approved changesets -- score normalized to 5
Inputs used
merged_prs143
open_issues5
closed_issues16
prs_merged_7d7
prs_decided_7d7
prs_merged_30d33
prs_decided_30d34
issue_closed_ratio0.762
closed_unmerged_prs36
first_time_authors_30d1
first_time_prs_merged_30d1
first_time_prs_decided_30d1
How it's scored
30/30Ownership backing — organization-owned
0/20Verified domain
16.7/25Owner reach — 208 followers of modelstudioai
8/25Track record — 9 public repos, account ~0 yr old
Inputs used
followers208
owner_typeOrganization
is_verifiedno
owner_loginmodelstudioai
public_repos9
account_age_days127

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 6 package(s) on npm
35/35Publish recency — latest publish 1 days ago
20/20Version history — 169 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesbailian-cli, bailian-cli-core, knowledge-studio-cli, bailian-cli-runtime, bailian-cli-commands, bailian-kb-dsh
ecosystemsnpm
any_deprecatedno
min_days_since_publish1

Engineering Quality

Are baseline engineering and documentation practices in place?

74Good · 19% of overall
How it's scored
24/24CI workflows — 3 workflow(s)
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
16/20OpenSSF Scorecard: CI-Tests — 7 out of 8 merged PRs checked by a CI test -- score normalized to 8
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://bailian.console.aliyun.com/cli
10/10Repository description
10/10Topics — 15 topics
0/10Wiki
Inputs used
topicsaliyun, cli, modelstudio, qwen, skills, ai-agent, ai-cli, bailian, command-line-tool, dashscope, llm-tools, mcp, mcp-server, text-to-image, text-to-video
has_wikino
homepagehttps://bailian.console.aliyun.com/cli
docs_sitehttps://bailian.console.aliyun.com/cli
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

50Moderate · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
2.2/7.5Branch-Protection — branch protection is not maximal on development and all release branches
2/2.5CI-Tests — 7 out of 8 merged PRs checked by a CI test -- score normalized to 8
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
3.8/7.5Code-Review — Found 4/8 approved changesets -- score normalized to 5
2.5/2.5Contributors — project has 5 contributing companies or organizations
10/10Dangerous-Workflow — no dangerous workflow patterns detected
0/7.5Dependency-Update-Tool — no update tool detected
0/5Fuzzing — project is not fuzzed
2.5/2.5License — license file detected
7.5/7.5Maintained — 30 commit(s) and 9 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
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 — Project has not signed or included provenance with any releases.
0/7.5Token-Permissions — detected GitHub workflow tokens with excessive permissions
0/7.5Vulnerabilities — 22 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated17
scorecard_versionv5.5.0
checks_inconclusive1
scorecard_aggregate3.8
Excluded from scoring (no data or not applicable): Packaging. Remaining weights renormalized.

Dependency advisories

100Exceptional
How it's scored
35/35Direct dependencies free of known advisories — no direct dependency carries a known advisory
25/25Indirect dependencies free of known advisories — no indirect dependency carries a known advisory
0/40No advisories left outstanding — no advisory carries a publication date
Inputs used
sourceosv
advisories0
affected_packages0
assessed_packages54
unassessed_packages0
affected_by_severitynone
direct_affected_packages0
Excluded from scoring (no data or not applicable): No advisories left outstanding. Remaining weights renormalized. Matched the npm:bailian-cli@1.25.0 runtime dependency closure — what installing the published package pulls in — 54 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.

68Good · 4% of overall
How it's scored
45/45Agent instructions — AGENTS.md, CLAUDE.md
0/15Machine-readable docs (llms.txt)
40/40Legible commit history — 88 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.88
agent_instruction_filesAGENTS.md, CLAUDE.md
agent_instruction_max_bytes12,862
How it's scored
0/18One-command bootstrap
22/22Automated tests
0/11Lint / format config
11/11Static type checking — packages/bailian-kb-dsh/tsconfig.json, packages/cli/tsconfig.json, packages/commands/tsconfig.json, packages/core/tsconfig.json, packages/kscli/tsconfig.json, packages/runtime/tsconfig.json, tsconfig.json
10/10Reproducible environment — lockfile
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 — dependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsyes
lockfilespnpm-lock.yaml
has_dockerfileno
typed_languageyes
bootstrap_files—
has_devcontainerno
has_linter_configno
typecheck_configspackages/bailian-kb-dsh/tsconfig.json, packages/cli/tsconfig.json, packages/commands/tsconfig.json, packages/core/tsconfig.json, packages/kscli/tsconfig.json, packages/runtime/tsconfig.json, tsconfig.json
agent_commit_share0
toolchain_manifests—
dependency_bot_commit_share0
How it's scored
45/45Type-checkable code — TypeScript (statically typed)
54.8/55Manageable file sizes — 3/692 source files over 60KB
Inputs used
primary_languageTypeScript
largest_source_bytes153,374
source_files_sampled692
oversized_source_files3

Key facts

332GitHub stars
15contributors
881commits, last 12 months
0days since last push
56releases
3bus factor
5open issues
npmpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • GitHub dependency-graph SBOM unavailable (404); the dependency graph may be disabled for this repository

More detail

Star and fork history 0 ★ / 28 ⇿
0Stars
28Forks
51Releases

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.

4812162024282852026-052026-072026-09
Major 0Minor 11Patch 7
OpenSSF Scorecard 3.8 / 10
3.8aggregate

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 02:49 UTC

10Binary-Artifactsno binaries found in the repo
3Branch-Protectionbranch protection is not maximal on development and all release branches
8CI-Tests7 out of 8 merged PRs checked by a CI test -- score normalized to 8
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
5Code-ReviewFound 4/8 approved changesets -- score normalized to 5
10Contributorsproject has 5 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained30 commit(s) and 9 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
0SASTSAST tool is not run on all commits -- score normalized to 0
0Security-Policysecurity policy file not detected
0Signed-ReleasesProject has not signed or included provenance with any releases.
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
0Vulnerabilities22 existing vulnerabilities detected
Direct dependencies 23
RegistryPackageVersion constraintManifest
npmyamlcatalog:packages/bailian-kb-dsh/package.json
npmbailian-cli-commandsworkspace:*packages/cli/package.json
npmbailian-cli-coreworkspace:*packages/cli/package.json
npmbailian-cli-runtimeworkspace:*packages/cli/package.json
npmtar-streamcatalog:packages/cli/package.json
npm@openagentpack/sdk0.7.1packages/commands/package.json
npmbailian-cli-coreworkspace:*packages/commands/package.json
npmbailian-cli-runtimeworkspace:*packages/commands/package.json
npmboxencatalog:packages/commands/package.json
npmchalkcatalog:packages/commands/package.json
npmsmol-tomlcatalog:packages/commands/package.json
npmyamlcatalog:packages/commands/package.json
npmtar-streamcatalog:packages/core/package.json
npmyaml^2.8.3packages/core/package.json
npmyauzlcatalog:packages/core/package.json
npmbailian-cli-coreworkspace:*packages/e2e/package.json
npmbailian-cli-commandsworkspace:*packages/kscli/package.json
npmbailian-cli-coreworkspace:*packages/kscli/package.json
npmbailian-cli-runtimeworkspace:*packages/kscli/package.json
npmbailian-cli-coreworkspace:*packages/runtime/package.json
npmboxencatalog:packages/runtime/package.json
npmchalkcatalog:packages/runtime/package.json
npmundicicatalog:packages/runtime/package.json
All dependencies not collected

The resolved dependency set could not be collected for this report: GitHub dependency-graph SBOM unavailable (404); the dependency graph may be disabled for this repository

Dependency advisories 0

Installing npm:bailian-cli@1.25.0 pulls in 54 packages, direct and transitive: 0 carry known advisories, of which 0 are direct dependencies.

No known advisories affect the assessed dependencies.

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.