Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-08 16:38 UTC

volcengine / ark-cli

The fastest way to put Volcengine Ark in your terminal and your AI agent — go from prompt to generated media, multimodal answer, or deployed endpoint in a single command, no API glue code.

PythonApache-2.0★ 120 stars⑂ 12 forkssince Jun 2026View on GitHub ↗

volcengine/ark-cli holds a health index of 45 out of 100, placing it in the Weak band. It scores highest on Vitality (71/100) and lowest on Security (24/100). It was last updated 1 day ago. A single contributor accounts for most of its recent work.

45
overall / 100
Weak

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.

45
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

VolcengineOrganization
2,079 followers208 public repossince Jun 2020

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

Package ecosystems

Metrics by category

Vitality

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

71Good · 21% of overall
How it's scored
36/36Push recency — last push 1 days ago
8.3/36Commit cadence — 12/52 weeks with commits
14.7/18Commit volume — 42 commits in the last year
0/10OpenSSF Scorecard: Maintained — project was created within the last 90 days. Please review its contents carefully
Inputs used
commits_last_year42
human_commit_share1
days_since_last_push1
active_weeks_last_year12
How it's scored
27/27Ships releases — 30 releases published
36/36Release recency — latest release 1 days ago
27/27Release cadence — a release every ~2.1 days
0/10OpenSSF Scorecard: Signed-Releases — Project has not signed or included provenance with any releases.
Inputs used
releases_count30
latest_release_tagv1.0.26
releases_from_tagsno
days_since_latest_release1
mean_days_between_releases2.1

Community & Adoption

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

46Weak · 17% of overall
How it's scored
33.7/60Stars — 120 stars
8.7/25Forks — 12 forks
0/15Watchers — 1 watchers
Inputs used
forks12
stars120
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)
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_servicesshields.io
has_pull_request_templateno
How it's scored
35.9/80Monthly downloads — 491 downloads/month across npm
0/20Registry dependents — not reported by this ecosystem
Inputs used
packages@volcengine/ark-plan-api, @volcengine/ark-managed-agents
dependents—
ecosystemsnpm
total_downloads—
monthly_downloads491
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?

60Moderate · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
2.5/22.5Commit distribution — top contributor authored 89% of commits
4.1/13.5Contributor breadth — 3 contributors
0/10OpenSSF Scorecard: Contributors — project has 0 contributing companies or organizations -- score normalized to 0
Inputs used
bus_factor1
contributors_sampled3
top_contributor_share0.889
How it's scored
29.4/42Issue resolution — 70% of issues closed
30/30PR acceptance — 3/3 decided PRs merged
13/13Newcomer PR acceptance — 3/3 first-time contributors' PRs merged in 30d
1.5/15OpenSSF Scorecard: Code-Review — Found 3/24 approved changesets -- score normalized to 1
Inputs used
merged_prs3
open_issues6
closed_issues14
prs_merged_7d0
prs_decided_7d0
prs_merged_30d3
prs_decided_30d3
issue_closed_ratio0.7
closed_unmerged_prs0
first_time_authors_30d1
first_time_prs_merged_30d3
first_time_prs_decided_30d3
How it's scored
30/30Ownership backing — organization-owned
0/20Verified domain
23.9/25Owner reach — 2,079 followers of volcengine
25/25Track record — 208 public repos, account ~6 yr old
Inputs used
followers2,079
owner_typeOrganization
is_verifiedno
owner_loginvolcengine
public_repos208
account_age_days2,267
How it's scored
25/25Published & resolvable — 2 package(s) on npm
35/35Publish recency — latest publish 13 days ago
4/20Version history — 1 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packages@volcengine/ark-plan-api, @volcengine/ark-managed-agents
ecosystemsnpm
any_deprecatedno
min_days_since_publish13

Engineering Quality

Are baseline engineering and documentation practices in place?

27At Risk · 19% of overall
How it's scored
0/24CI workflows
0/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Tests — 0 out of 3 merged PRs checked by a CI test -- score normalized to 0
Inputs used
has_cino
has_testsno
has_editorconfigno
has_linter_configno
has_precommit_configno
How it's scored
30/30README
0/25Documentation directory
15/15Documentation / homepage site — https://www.volcengine.com/product/ark
10/10Repository description
10/10Topics — 11 topics
0/10Wiki
Inputs used
topicsai-agent, ai-skills, ark, cli, doubao, llm, multimodal, text-to-image, text-to-video, volcengine, dsh-plugin
has_wikino
homepage—
docs_sitehttps://www.volcengine.com/product/ark
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

24At Risk · 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 3 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 3/24 approved changesets -- score normalized to 1
0/2.5Contributors — project has 0 contributing companies or organizations -- score normalized to 0
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 — project was created within the last 90 days. Please review its contents carefully
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 — Project has not signed or included provenance with any releases.
0/7.5Token-Permissions — no data
7.5/7.5Vulnerabilities — 0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated14
scorecard_versionv5.5.0
checks_inconclusive4
scorecard_aggregate2.4
Excluded from scoring (no data or not applicable): Dangerous-Workflow, Packaging, Pinned-Dependencies, 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.

40Weak · 4% of overall
How it's scored
45/45Agent instructions — skills/arkcli-agent/references/agent.md
0/15Machine-readable docs (llms.txt)
40/40Legible commit history — 41 of 42 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.976
agent_instruction_filesskills/arkcli-agent/references/agent.md
agent_instruction_max_bytes19,044
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 practice — no agent-authored commits among the last 42
0/8Automated maintenance — no automated dependency updates observed
0/10OpenSSF Scorecard: Pinned-Dependencies — no data
Inputs used
has_nixno
has_testsno
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 — Python without a type-check config
55/55Manageable file sizes — 0/1 source files over 60KB
Inputs used
primary_languagePython
largest_source_bytes440
source_files_sampled1
oversized_source_files0

Key facts

120GitHub stars
3contributors
42commits, last 12 months
1days since last push
30releases
1bus factor
6open issues
—package 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 ★ / 12 ⇿
0Stars
12Forks
24Releases

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.

0246810121212026-062026-082026-09
Major 0Minor 0Patch 23
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-09-08 16:38 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
0CI-Tests0 out of 3 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 3/24 approved changesets -- score normalized to 1
0Contributorsproject has 0 contributing companies or organizations -- score normalized to 0
n/aDangerous-Workflowno workflows found
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
0Maintainedproject was created within the last 90 days. Please review its contents carefully
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
0Signed-ReleasesProject has not signed or included provenance with any releases.
n/aToken-PermissionsNo tokens found
10Vulnerabilities0 existing vulnerabilities detected
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

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.