Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-10-02 22:52 UTC

arcships / aimux

Unified LLM access layer in Rust — one API for 325 AI providers. 统一 LLM 服务接入层:一套 API 接入 325 家 AI 服务商。

RustMIT★ 195 stars⑂ 11 forkssince Jul 2026View on GitHub ↗
KindLibraryMobile applicationhow this is determined

arcships/aimux holds a health index of 77 out of 100, placing it in the Good band. It scores highest on Engineering Quality (90/100) and lowest on Security (38/100). It was last updated today. A single contributor accounts for most of its recent work.

77
overall / 100
Good

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.

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

Ownership

arcshipsOrganization
22 followers10 public repossince Apr 2026

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?

72Good · 21% of overall
How it's scored
36/36Push recency — last push 0 days ago
5.5/36Commit cadence — 8/52 weeks with commits
18/18Commit volume — 405 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_year405
human_commit_share1
days_since_last_push0
active_weeks_last_year8
How it's scored
27/27Ships releases — 4 releases published
36/36Release recency — latest release 4 days ago
27/27Release cadence — a release every ~18.6 days
0/10OpenSSF Scorecard: Signed-Releases — Project has not signed or included provenance with any releases.
Inputs used
releases_count4
latest_release_tagv0.5.0
releases_from_tagsno
days_since_latest_release4
mean_days_between_releases18.6

Community & Adoption

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

68Good · 17% of overall
How it's scored
37.1/60Stars — 195 stars
8.3/25Forks — 11 forks
1.7/15Watchers — 3 watchers
Inputs used
forks11
stars195
watchers3
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history

Community health

92Excellent
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (MIT)
18/18CONTRIBUTING guide
13.5/13.5Code of conduct
0/7.2Issue template
6.3/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges11
has_contributingyes
has_issue_templateno
has_code_of_conductyes
readme_badge_servicesgithub.com, pkg.go.dev, shields.io
has_pull_request_templateyes

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
1.8/22.5Commit distribution — top contributor authored 92% of commits
6.8/13.5Contributor breadth — 5 contributors
3/10OpenSSF Scorecard: Contributors — project has 1 contributing companies or organizations -- score normalized to 3
Inputs used
bus_factor1
contributors_sampled5
top_contributor_share0.919
How it's scored
35.8/42Issue resolution — 85% of issues closed
26.2/30PR acceptance — 109/125 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
4.5/15OpenSSF Scorecard: Code-Review — Found 11/30 approved changesets -- score normalized to 3
Inputs used
merged_prs109
open_issues11
closed_issues64
prs_merged_7d6
prs_decided_7d13
prs_merged_30d12
prs_decided_30d22
issue_closed_ratio0.853
closed_unmerged_prs16
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
9.8/25Owner reach — 22 followers of arcships
8.6/25Track record — 10 public repos, account ~0 yr old
Inputs used
followers22
owner_typeOrganization
is_verifiedno
owner_loginarcships
public_repos10
account_age_days184

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 5 package(s) on crates
35/35Publish recency — latest publish 4 days ago
20/20Version history — 8 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesaimux-ffi, aimux-core, aimux-stream, aimux-providers, aimux-provider-utils
ecosystemscrates
any_deprecatedno
min_days_since_publish4

Engineering Quality

Are baseline engineering and documentation practices in place?

90Excellent · 19% of overall
How it's scored
24/24CI workflows — 2 workflow(s)
24/24Tests present
16/16Linter config — Cargo.toml ([workspace.lints]), aimux-core/Cargo.toml ([lints]), aimux-ffi/Cargo.toml ([lints]), aimux-provider-utils/Cargo.toml ([lints]), aimux-providers/Cargo.toml ([lints]), aimux-stream/Cargo.toml ([lints]), rustfmt.toml
0/9.6Pre-commit hooks
0/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests — 30 out of 30 merged PRs checked by a CI test -- score normalized to 10
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configyes
has_precommit_configno

Documentation

100Exceptional
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage site — https://docs.rs/aimux-ffi
10/10Repository description
10/10Topics — 14 topics
10/10Wiki
Inputs used
topicsai, c, flutter, go, java, kotlin, llm, llm-api, llm-providers, nodejs, openai-compatible, python, rust, swift
has_wikiyes
homepage—
docs_sitehttps://docs.rs/aimux-ffi
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

38Weak · 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.5/2.5CI-Tests — 30 out of 30 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
2.2/7.5Code-Review — Found 11/30 approved changesets -- score normalized to 3
0.8/2.5Contributors — project has 1 contributing companies or organizations -- score normalized to 3
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
0/7.5Maintained — project was created within the last 90 days. Please review its contents carefully
5/5Packaging — packaging workflow detected
0.5/5Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 1
0/5SAST — SAST tool is not run on all commits -- score normalized to 0
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
1.5/7.5Vulnerabilities — 8 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated18
scorecard_versionv5.5.0
checks_inconclusive0
scorecard_aggregate3.8

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.

72Good · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
40/40Legible commit history — 100 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share1
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
12.6/18One-command bootstrap — Cargo.toml, aimux-core/Cargo.toml, aimux-ffi/Cargo.toml (toolchain convention, no task runner)
22/22Automated tests
11/11Lint / format config — Cargo.toml ([workspace.lints]), aimux-core/Cargo.toml ([lints]), aimux-ffi/Cargo.toml ([lints]), aimux-provider-utils/Cargo.toml ([lints]), aimux-providers/Cargo.toml ([lints]), aimux-stream/Cargo.toml ([lints]), rustfmt.toml
11/11Static type checking — bindings/node/tsconfig.json, tools/aimux-web/web/tsconfig.json
10/10Reproducible environment — lockfile
8/10Demonstrated agent practice — 4 of the last 100 commits agent-authored or agent-credited
0/8Automated maintenance — no automated dependency updates observed
1/10OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 1
Inputs used
has_nixno
has_testsyes
lockfilespackage-lock.json
has_dockerfileno
typed_languageyes
bootstrap_files—
has_devcontainerno
has_linter_configyes
typecheck_configsbindings/node/tsconfig.json, tools/aimux-web/web/tsconfig.json
agent_commit_share0.04
toolchain_manifestsCargo.toml, aimux-core/Cargo.toml, aimux-ffi/Cargo.toml, aimux-provider-utils/Cargo.toml, aimux-providers/Cargo.toml, aimux-stream/Cargo.toml, bindings/flutter/android/build.gradle, bindings/flutter/example/android/app/build.gradle.kts, bindings/flutter/example/android/build.gradle.kts, bindings/go/go.mod, bindings/java/build.gradle.kts, bindings/kotlin/build.gradle.kts, bindings/node/Cargo.toml, bindings/python/Cargo.toml, docs/internal/cache-tracing/prototype/Cargo.toml, tools/aimux-cli/Cargo.toml, tools/aimux-replay/Cargo.toml, tools/aimux-web/Cargo.toml
dependency_bot_commit_share0
How it's scored
45/45Type-checkable code — Rust (statically typed)
53.3/55Manageable file sizes — 28/928 source files over 60KB
Inputs used
primary_languageRust
largest_source_bytes224,176
source_files_sampled928
oversized_source_files28
How it's scored
0/40API schema (OpenAPI/GraphQL/proto) — not applicable to this kind of software
20/20MCP server
40/40Runnable examples — example, examples
Inputs used
example_dirsexample, examples
has_mcp_signalyes
api_schema_files—
interfaces_expected_of—
Excluded from scoring (no data or not applicable): API schema (OpenAPI/GraphQL/proto). Remaining weights renormalized.

Key facts

195GitHub stars
5contributors
405commits, last 12 months
0days since last push
4releases
1bus factor
11open issues
crates.iopackage 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 ★ / 11 ⇿
0Stars
11Forks
3Releases

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.

048121132026-082026-082026-09
Major 0Minor 2Patch 1
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-10-02 22:51 UTC

10Binary-Artifactsno binaries found in the repo
3Branch-Protectionbranch protection is not maximal on development and all release branches
10CI-Tests30 out of 30 merged PRs checked by a CI test -- score normalized to 10
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
3Code-ReviewFound 11/30 approved changesets -- score normalized to 3
3Contributorsproject has 1 contributing companies or organizations -- score normalized to 3
10Dangerous-Workflowno dangerous workflow patterns detected
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
10Packagingpackaging workflow detected
1Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 1
0SASTSAST tool is not run on all commits -- score normalized to 0
10Security-Policysecurity policy file detected
0Signed-ReleasesProject has not signed or included provenance with any releases.
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
2Vulnerabilities8 existing vulnerabilities detected
Direct dependencies 67
RegistryPackageVersion constraintManifest
crates.ioserde—aimux-core/Cargo.toml
crates.ioserde_json—aimux-core/Cargo.toml
crates.ioasync-trait—aimux-core/Cargo.toml
crates.iothiserror—aimux-core/Cargo.toml
crates.iofutures—aimux-core/Cargo.toml
crates.ioasync-stream—aimux-core/Cargo.toml
crates.iotracing—aimux-core/Cargo.toml
crates.iots-rs—aimux-core/Cargo.toml
crates.iotokio1aimux-core/Cargo.toml
crates.iotokio-util0.7aimux-core/Cargo.toml
crates.iohttpdate—aimux-core/Cargo.toml
crates.iorand—aimux-core/Cargo.toml
crates.iobase640.22aimux-core/Cargo.toml
crates.iojsonschema—aimux-core/Cargo.toml
crates.ioaimux-core—aimux-ffi/Cargo.toml
crates.ioaimux-providers—aimux-ffi/Cargo.toml
crates.ioaimux-provider-utils—aimux-ffi/Cargo.toml
crates.ioserde—aimux-ffi/Cargo.toml
crates.ioserde_json—aimux-ffi/Cargo.toml
crates.iotokio—aimux-ffi/Cargo.toml
crates.iotracing—aimux-ffi/Cargo.toml
crates.iofutures—aimux-ffi/Cargo.toml
crates.ioasync-stream—aimux-ffi/Cargo.toml
crates.ioaimux-core—aimux-provider-utils/Cargo.toml
crates.ioaimux-stream—aimux-provider-utils/Cargo.toml
crates.ioreqwest—aimux-provider-utils/Cargo.toml
crates.iohttp1aimux-provider-utils/Cargo.toml
crates.ioserde—aimux-provider-utils/Cargo.toml
crates.ioserde_json—aimux-provider-utils/Cargo.toml
crates.iotokio—aimux-provider-utils/Cargo.toml
crates.iotracing—aimux-provider-utils/Cargo.toml
crates.iotracing-subscriber—aimux-provider-utils/Cargo.toml
crates.iobytes—aimux-provider-utils/Cargo.toml
crates.iofutures—aimux-provider-utils/Cargo.toml
crates.ioasync-stream—aimux-provider-utils/Cargo.toml
crates.iourl—aimux-provider-utils/Cargo.toml
crates.iochrono0.4aimux-provider-utils/Cargo.toml
crates.iotokio-tungstenite—aimux-provider-utils/Cargo.toml
crates.iorustls0.23aimux-provider-utils/Cargo.toml
crates.iowebpki-roots0.26aimux-provider-utils/Cargo.toml
crates.iobase640.22aimux-provider-utils/Cargo.toml
crates.ioaimux-core—aimux-providers/Cargo.toml
crates.ioaimux-stream—aimux-providers/Cargo.toml
crates.ioaimux-provider-utils—aimux-providers/Cargo.toml
crates.ioasync-trait—aimux-providers/Cargo.toml
crates.ioserde—aimux-providers/Cargo.toml
crates.ioserde_json—aimux-providers/Cargo.toml
crates.ioreqwest—aimux-providers/Cargo.toml
crates.iotokio—aimux-providers/Cargo.toml
crates.iofutures—aimux-providers/Cargo.toml
crates.iobytes—aimux-providers/Cargo.toml
crates.iotracing—aimux-providers/Cargo.toml
crates.ioasync-stream—aimux-providers/Cargo.toml
crates.iobase640.22aimux-providers/Cargo.toml
crates.iosha20.10aimux-providers/Cargo.toml
crates.iohmac0.12aimux-providers/Cargo.toml
crates.iohex0.4aimux-providers/Cargo.toml
crates.iochrono0.4aimux-providers/Cargo.toml
crates.iourl—aimux-providers/Cargo.toml
crates.iopercent-encoding2aimux-providers/Cargo.toml
crates.iofutures—aimux-stream/Cargo.toml
crates.iotokio—aimux-stream/Cargo.toml
crates.iopin-project-lite—aimux-stream/Cargo.toml
crates.iobytes—aimux-stream/Cargo.toml
crates.ioserde—aimux-stream/Cargo.toml
crates.ioserde_json—aimux-stream/Cargo.toml
crates.iothiserror—aimux-stream/Cargo.toml
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 — crates.io.