Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-11-17 05:10 UTC

satoraHQ / satora-sdk

Rust · TypeScriptMIT★ 7 stars⑂ 5 forkssince Dec 2025View on GitHub ↗

satoraHQ/satora-sdk holds a health index of 54 out of 100, placing it in the Moderate band. It scores highest on Vitality (95/100) and lowest on Community & Adoption (33/100). It was last updated today. A single contributor accounts for most of its recent work.

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

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

Ownership

satoraOrganization · verified domain
31 followers28 public repossince Jul 2024

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

Metrics by category

Vitality

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

95Exceptional · 21% of overall
How it's scored
36/36Push recency — last push 0 days ago
35.3/36Commit cadence — 51/52 weeks with commits
18/18Commit volume — 1,033 commits in the last year
10/10OpenSSF Scorecard: Maintained — 30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year1,033
human_commit_share0.9
days_since_last_push0
active_weeks_last_year51
How it's scored
27/27Ships releases — 14 releases published
27/36Release recency — latest release 146 days ago
27/27Release cadence — a release every ~3.2 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count14
latest_release_tagv0.2.44
releases_from_tagsno
days_since_latest_release146
mean_days_between_releases3.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?

33At Risk · 17% of overall
How it's scored
12.6/60Stars — 7 stars
5/25Forks — 5 forks
0/15Watchers — 0 watchers
Inputs used
forks5
stars7
watchers0
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (MIT)
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

Sustainability & Governance

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

38Weak · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
7.2/22.5Commit distribution — top contributor authored 68% of commits
5.4/13.5Contributor breadth — 4 contributors
10/10OpenSSF Scorecard: Contributors — project has 3 contributing companies or organizations -- score normalized to 10
Inputs used
bus_factor1
contributors_sampled4
top_contributor_share0.679
How it's scored
0/42Issue resolution — 0% of issues closed
7.5/30PR acceptance — 1/4 decided PRs merged
0/13Newcomer PR acceptance — 0/1 first-time contributors' PRs merged in 30d
0/15OpenSSF Scorecard: Code-Review — Found 0/30 approved changesets -- score normalized to 0
Inputs used
merged_prs1
open_issues2
closed_issues0
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d1
issue_closed_ratio0
closed_unmerged_prs3
first_time_authors_30d1
first_time_prs_merged_30d0
first_time_prs_decided_30d1
How it's scored
30/30Ownership backing — organization-owned
20/20Verified domain
10.8/25Owner reach — 31 followers of satoraHQ
15.4/25Track record — 28 public repos, account ~2 yr old
Inputs used
followers31
owner_typeOrganization
is_verifiedyes
owner_loginsatoraHQ
public_repos28
account_age_days867

Engineering Quality

Are baseline engineering and documentation practices in place?

46Weak · 19% of overall
How it's scored
0/24CI workflows
24/24Tests present
16/16Linter config — biome.json
0/9.6Pre-commit hooks
0/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Tests — no data
Inputs used
has_cino
has_testsyes
has_editorconfigno
has_linter_configyes
has_precommit_configno
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: CI-Tests. Remaining weights renormalized.
How it's scored
30/30README
0/25Documentation directory
0/15Documentation / homepage site
0/10Repository description
0/10Topics
10/10Wiki
Inputs used
topics—
has_wikiyes
homepage—
docs_site—
has_readmeyes
has_docs_dirno
has_descriptionno

Security

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

43Weak · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
3.8/7.5Branch-Protection — branch protection is not maximal on development and all release branches
0/2.5CI-Tests — no data
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
0/7.5Code-Review — Found 0/30 approved changesets -- score normalized to 0
2.5/2.5Contributors — project has 3 contributing companies or organizations -- score normalized to 10
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
7.5/7.5Maintained — 30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
0/5Packaging — no data
0/5Pinned-Dependencies — no data
0/5SAST — no SAST tool detected
5/5Security-Policy — security policy file detected
0/7.5Signed-Releases — no data
0/7.5Token-Permissions — no data
0/7.5Vulnerabilities — 101 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated12
scorecard_versionv5.5.0
checks_inconclusive6
scorecard_aggregate4.3
Excluded from scoring (no data or not applicable): CI-Tests, Dangerous-Workflow, Packaging, Pinned-Dependencies, Signed-Releases, 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.

74Good · 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 — 88 of 90 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.978
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
18/18One-command bootstrap — Justfile, dotnet-sdk/Justfile
22/22Automated tests
11/11Lint / format config — biome.json
11/11Static type checking — ts-pure-sdk/tsconfig.json, ts-sdk/packages/escrow-client/tsconfig.json, ts-sdk/packages/escrow/tsconfig.json, ts-sdk/packages/swap/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 — no data
Inputs used
has_nixno
has_testsyes
lockfilesCargo.lock, package-lock.json, pnpm-lock.yaml
has_dockerfileno
typed_languageyes
bootstrap_filesJustfile, dotnet-sdk/Justfile
has_devcontainerno
has_linter_configyes
typecheck_configsts-pure-sdk/tsconfig.json, ts-sdk/packages/escrow-client/tsconfig.json, ts-sdk/packages/escrow/tsconfig.json, ts-sdk/packages/swap/tsconfig.json
agent_commit_share0
toolchain_manifestsdotnet-sdk/Satora.Sdk.Cli/Satora.Sdk.Cli.csproj, dotnet-sdk/Satora.Sdk.Tests/Satora.Sdk.Tests.csproj, dotnet-sdk/Satora.Sdk/Satora.Sdk.csproj, dotnet-sdk/native/Cargo.toml, rust-sdk/Cargo.toml
dependency_bot_commit_share0
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: Pinned-Dependencies. Remaining weights renormalized.
How it's scored
45/45Type-checkable code — Rust (statically typed)
53.4/55Manageable file sizes — 11/367 source files over 60KB
Inputs used
primary_languageRust
largest_source_bytes373,256
source_files_sampled367
oversized_source_files11
How it's scored
40/40API schema (OpenAPI/GraphQL/proto) — rust-sdk/openapi.json, ts-pure-sdk/openapi.json
0/20MCP server — not applicable to this kind of software
40/40Runnable examples — examples
Inputs used
example_dirsexamples
has_mcp_signalno
api_schema_filesrust-sdk/openapi.json, ts-pure-sdk/openapi.json
interfaces_expected_of—
Excluded from scoring (no data or not applicable): MCP server. Remaining weights renormalized.

Key facts

7GitHub stars
4contributors
1,033commits, last 12 months
0days since last push
14releases
1bus factor
2open issues
crates.io, npmpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • Could not fetch crates package 'satora-rust-sdk' from its registry
  • Could not fetch crates package 'satora-sdk-ffi' from its registry
  • Could not fetch nuget package 'Satora.Sdk' from its registry
  • GitHub dependency-graph SBOM unavailable (404); the dependency graph may be disabled for this repository

More detail

Star and fork history 0 ★ / 5 ⇿
0Stars
5Forks
14Releases

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.

12345512026-012026-062026-11
Major 0Minor 0Patch 14
OpenSSF Scorecard 4.3 / 10
4.3aggregate

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-11-17 05:09 UTC

10Binary-Artifactsno binaries found in the repo
5Branch-Protectionbranch protection is not maximal on development and all release branches
n/aCI-Testsno pull request found
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0Code-ReviewFound 0/30 approved changesets -- score normalized to 0
10Contributorsproject has 3 contributing companies or organizations -- score normalized to 10
n/aDangerous-Workflowno workflows found
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
n/aPackagingpackaging workflow not detected
n/aPinned-Dependenciesno dependencies found
0SASTno SAST tool detected
10Security-Policysecurity policy file detected
n/aSigned-Releasesno releases found
n/aToken-PermissionsNo tokens found
0Vulnerabilities101 existing vulnerabilities detected
Direct dependencies 51
RegistryPackageVersion constraintManifest
crates.iobip392rust-sdk/Cargo.toml
crates.iobitcoin0.32rust-sdk/Cargo.toml
crates.ioelectrum-client0.24.1rust-sdk/Cargo.toml
crates.iofutures-util0.3rust-sdk/Cargo.toml
crates.iohex0.4rust-sdk/Cargo.toml
crates.iolightning-invoice0.33.2rust-sdk/Cargo.toml
crates.ionum-bigint0.4rust-sdk/Cargo.toml
crates.ionum-traits0.2rust-sdk/Cargo.toml
crates.ioreqwest0.13rust-sdk/Cargo.toml
crates.ioserde1rust-sdk/Cargo.toml
crates.ioserde_json1rust-sdk/Cargo.toml
crates.iosha20.10rust-sdk/Cargo.toml
crates.iothiserror1rust-sdk/Cargo.toml
crates.iotiny-keccak2rust-sdk/Cargo.toml
crates.iotokio-tungstenite0.28rust-sdk/Cargo.toml
crates.iotracing0.1rust-sdk/Cargo.toml
crates.iourl2rust-sdk/Cargo.toml
crates.iouuid1rust-sdk/Cargo.toml
crates.ioalloy1rust-sdk/Cargo.toml
crates.ioalloy-dyn-abi1rust-sdk/Cargo.toml
crates.ioalloy-provider1rust-sdk/Cargo.toml
crates.iorand0.8rust-sdk/Cargo.toml
crates.iorusqlite0.32rust-sdk/Cargo.toml
crates.iotokio1rust-sdk/Cargo.toml
crates.ioark-bdk-wallet0.12.1rust-sdk/Cargo.toml
crates.ioark-fees0.12.1rust-sdk/Cargo.toml
crates.ioark-rs0.12.1rust-sdk/Cargo.toml
crates.ioesplora-client0.11rust-sdk/Cargo.toml
crates.iorustls0.23rust-sdk/Cargo.toml
npm@arkade-os/sdk^0.5.5ts-pure-sdk/package.json
npm@noble/curves^2.2.0ts-pure-sdk/package.json
npm@noble/hashes^2.2.0ts-pure-sdk/package.json
npm@scure/base^2.0.0ts-pure-sdk/package.json
npm@scure/bip32^2.0.1ts-pure-sdk/package.json
npm@scure/bip39^2.0.1ts-pure-sdk/package.json
npm@scure/btc-signer^2.0.1ts-pure-sdk/package.json
npm@zerodev/sdk^5.5.0ts-pure-sdk/package.json
npmdexie4.4.4ts-pure-sdk/package.json
npmopenapi-fetch^0.17.0ts-pure-sdk/package.json
npmviem2.52.2ts-pure-sdk/package.json
NuGetMicrosoft.NET.Test.Sdk17.11.1dotnet-sdk/Satora.Sdk.Tests/Satora.Sdk.Tests.csproj
NuGetxunit2.9.2dotnet-sdk/Satora.Sdk.Tests/Satora.Sdk.Tests.csproj
NuGetxunit.runner.visualstudio2.8.2dotnet-sdk/Satora.Sdk.Tests/Satora.Sdk.Tests.csproj
crates.iobitcoin0.32dotnet-sdk/native/Cargo.toml
crates.iolendaswap_sdk—dotnet-sdk/native/Cargo.toml
crates.ioserde_json1dotnet-sdk/native/Cargo.toml
crates.iothiserror1dotnet-sdk/native/Cargo.toml
crates.iotokio1dotnet-sdk/native/Cargo.toml
crates.iotracing-subscriber0.3dotnet-sdk/native/Cargo.toml
crates.iouniffi0.29dotnet-sdk/native/Cargo.toml
crates.iourl2dotnet-sdk/native/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.