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

smartive / zitadel-rust

An implementation of the ZITADEL gRPC API in Rust. Complemented with other useful elements such as ServiceAccount auth.

RustCustom license★ 86 stars⑂ 31 forkssince Feb 2022View on GitHub ↗
KindNetwork serviceLibraryhow this is determined

smartive/zitadel-rust holds a health index of 56 out of 100, placing it in the Moderate band. It scores highest on Sustainability & Governance (65/100) and lowest on Security (46/100). It was last updated 5 days ago. A single contributor accounts for most of its recent work.

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

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

Ownership

smartiveOrganization · verified domain
18 followers68 public repossince Nov 2012

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
crates.iozitadelpoints to another repo — not scored5.7.712,47014050 days agoauthenticationclientsgrpcoidczitadelapi-bindings

Metrics by category

Vitality

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

62Moderate · 21% of overall
How it's scored
36/36Push recency — last push 5 days ago
3.9/36Commit cadence — 9/52 weeks with commits, discounted for automation: 25 of the last 100 commits human-authored, spanning 160 days
6.4/18Commit volume — 13 commits in the last year, discounted for automation: 25 of the last 100 commits human-authored, spanning 160 days
2/10OpenSSF Scorecard: Maintained — 3 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 2
Inputs used
commits_last_year13
human_commit_share0.25
days_since_last_push5
active_weeks_last_year9
How it's scored
27/27Ships releases — 100 releases published
36/36Release recency — latest release 50 days ago
19.8/27Release cadence — a release every ~74.1 days
0/10OpenSSF Scorecard: Signed-Releases — Project has not signed or included provenance with any releases.
Inputs used
releases_count100
latest_release_tagv5.7.7
releases_from_tagsno
days_since_latest_release50
mean_days_between_releases74.1

Community & Adoption

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

46Weak · 17% of overall
How it's scored
31.3/60Stars — 86 stars
12.3/25Forks — 31 forks
4.3/15Watchers — 7 watchers
Inputs used
forks31
stars86
watchers7
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
16.9/22.5License — license file present, not a recognized license
0/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges4
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_servicesshields.io
has_pull_request_templateno

Sustainability & Governance

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

65Good · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
11/22.5Commit distribution — top contributor authored 51% of commits
13.5/13.5Contributor breadth — 16 contributors
10/10OpenSSF Scorecard: Contributors — project has 4 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled16
top_contributor_share0.511
How it's scored
28.4/42Issue resolution — 68% of issues closed
28.1/30PR acceptance — 547/585 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_prs547
open_issues12
closed_issues25
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio0.676
closed_unmerged_prs38
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
20/20Verified domain
9.2/25Owner reach — 18 followers of smartive
25/25Track record — 68 public repos, account ~13 yr old
Inputs used
followers18
owner_typeOrganization
is_verifiedyes
owner_loginsmartive
public_repos68
account_age_days5,042

Engineering Quality

Are baseline engineering and documentation practices in place?

46Weak · 19% of overall
How it's scored
24/24CI workflows — 2 workflow(s)
0/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
10/20OpenSSF Scorecard: CI-Tests — 13 out of 26 merged PRs checked by a CI test -- score normalized to 5
Inputs used
has_ciyes
has_testsno
has_editorconfigno
has_linter_configno
has_precommit_configno
How it's scored
30/30README
0/25Documentation directory
15/15Documentation / homepage site — https://docs.rs/zitadel/latest/zitadel/
10/10Repository description
10/10Topics — 8 topics
0/10Wiki
Inputs used
topicsgrpc, zitadel, rust, rust-crate, api, authn, authz, client
has_wikino
homepagehttps://docs.rs/zitadel/latest/zitadel/
docs_sitehttps://docs.rs/zitadel/latest/zitadel/
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

46Weak · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
0/7.5Branch-Protection — no data
1.2/2.5CI-Tests — 13 out of 26 merged PRs checked by a CI test -- score normalized to 5
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
2.5/2.5Contributors — project has 4 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.2/2.5License — license file detected
1.5/7.5Maintained — 3 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 2
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
7.5/7.5Vulnerabilities — 0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate4.6
Excluded from scoring (no data or not applicable): Branch-Protection, Packaging. 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.

48Weak · 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 — 25 of 25 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
18/18One-command bootstrap — justfile
0/22Automated tests
0/11Lint / format config
11/11Static type checking — Rust (statically typed)
0/10Reproducible environment
0/10Demonstrated agent practice — no agent-authored commits among the last 100
8/8Automated maintenance — 75 of the last 100 commits are automated dependency updates
0/10OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsno
lockfiles—
has_dockerfileno
typed_languageyes
bootstrap_filesjustfile
has_devcontainerno
has_linter_configno
typecheck_configs—
agent_commit_share0
toolchain_manifestsCargo.toml
dependency_bot_commit_share0.75
How it's scored
45/45Type-checkable code — Rust (statically typed)
55/55Manageable file sizes — 0/36 source files over 60KB
Inputs used
primary_languageRust
largest_source_bytes24,903
source_files_sampled36
oversized_source_files0
How it's scored
0/40API schema (OpenAPI/GraphQL/proto)
0/20MCP server
40/40Runnable examples — examples
Inputs used
example_dirsexamples
has_mcp_signalno
api_schema_files—
interfaces_expected_ofnetwork-service

Key facts

86GitHub stars
16contributors
13commits, last 12 months
5days since last push
100releases
1bus factor
12open issues
crates.iopackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • crates package 'zitadel' points at a different repository (https://github.com/buehler/zitadel-rust); excluded from ecosystem scoring
  • No resolved dependencies carried a version and a supported ecosystem

More detail

Star and fork history 0 ★ / 31 ⇿
0Stars
31Forks
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.

0510152025303012022-112024-092026-07
Major 2Minor 13Patch 84

Each point covers 4 days.

OpenSSF Scorecard 4.6 / 10
4.6aggregate

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-13 16:10 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
5CI-Tests13 out of 26 merged PRs checked by a CI test -- score normalized to 5
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
3Code-ReviewFound 11/30 approved changesets -- score normalized to 3
10Contributorsproject has 4 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
9Licenselicense file detected
2Maintained3 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 2
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
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 24
RegistryPackageVersion constraintManifest
crates.ioactix-web4.5.1Cargo.toml
crates.ioasync-trait0.1.80Cargo.toml
crates.ioaxum0.8.0Cargo.toml
crates.ioaxum-extra0.12.0Cargo.toml
crates.iobase64-compat1Cargo.toml
crates.iocustom_error1.9.2Cargo.toml
crates.iodocument-features0.2.8Cargo.toml
crates.iojsonwebtoken11.0.0Cargo.toml
crates.iomoka0.12.8Cargo.toml
crates.ioopenidconnect4.0.0Cargo.toml
crates.iopbjson-types0.9.0Cargo.toml
crates.ioprost0.14.1Cargo.toml
crates.ioprost-types0.14.1Cargo.toml
crates.iotonic-prost0.14.2Cargo.toml
crates.ioreqwest0.12.12Cargo.toml
crates.iorocket0.5.0Cargo.toml
crates.ioserde1.0.200Cargo.toml
crates.ioserde_json1.0.116Cargo.toml
crates.ioserde_urlencoded0.7.1Cargo.toml
crates.iotime0.3.36Cargo.toml
crates.iotokio1.37.0Cargo.toml
crates.iotonic0.14.2Cargo.toml
crates.iorocket_okapi0.9.0Cargo.toml
crates.ioschemars0.8.21Cargo.toml
All dependencies 27

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

RegistryPackageVersionRelation
crates.ioactix-web—direct
crates.ioasync-trait—direct
crates.ioaxum—direct
crates.ioaxum-extra—direct
crates.iobase64-compat—direct
crates.iocustom_error—direct
crates.iodocument-features—direct
crates.iojsonwebtoken—direct
crates.iomoka—direct
crates.ioopenidconnect—direct
crates.iopbjson-types—direct
crates.ioprost—direct
crates.ioprost-types—direct
crates.ioreqwest—direct
crates.iorocket—direct
crates.iorocket_okapi—direct
crates.ioschemars—direct
crates.ioserde—direct
crates.ioserde_json—direct
crates.ioserde_urlencoded—direct
crates.iotime—direct
crates.iotokio—direct
crates.iotonic—direct
crates.iotonic-prost—direct
crates.iochrono—indirect
crates.iohttp-body-util—indirect
crates.iotower—indirect
Dependency advisories not assessed

Advisory matching could not run for this report: No resolved dependencies carried a version and a supported ecosystem

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.