Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-19 06:14 UTC

iotaledger / product-core

Rust · MoveApache-2.0★ 0 stars⑂ 2 forkssince Apr 2025View on GitHub ↗

iotaledger/product-core holds a health index of 81 out of 100, placing it in the Excellent band. It scores highest on Vitality (88/100) and lowest on Community & Adoption (46/100). It was last updated today. 3 contributors account for most of its recent work.

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.

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)

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

Ownership

IOTAOrganization · verified domain

820 followers108 public repossince Jun 2016

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?

88Excellent · 21% of overall

Development activity

88Excellent

How it's scored

36/36	Push recency — last push 0 days ago
23.5/36	Commit cadence — 34/52 weeks with commits
18/18	Commit volume — 130 commits in the last year
10/10	OpenSSF Scorecard: Maintained — 29 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10

Inputs used

commits_last_year	130
human_commit_share	1
days_since_last_push	0
active_weeks_last_year	34

Release discipline

88Excellent

How it's scored

16.2/27	Ships releases — 30 version tags (no GitHub releases)
36/36	Release recency — latest release 29 days ago
27/27	Release cadence — a release every ~14.7 days
0/10	OpenSSF Scorecard: Signed-Releases — no data

Inputs used

releases_count	30
latest_release_tag	v0.8.24
releases_from_tags	yes
days_since_latest_release	29
mean_days_between_releases	14.7

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?

46Weak · 17% of overall

Popularity & adoption

5Critical

How it's scored

0/60	Stars — 0 stars
0/25	Forks — 2 forks
5/15	Watchers — 9 watchers

Inputs used

forks	2
stars	0
watchers	9
growth_state	unverified
growth_factor_pct	100
growth_unverified_reason	no_history

Community health

92Excellent

How it's scored

22.5/22.5	README
22.5/22.5	License — recognized license (Apache-2.0)
18/18	CONTRIBUTING guide
13.5/13.5	Code of conduct
0/7.2	Issue template
6.3/6.3	PR template

Inputs used

has_readme	yes
has_license	yes
readme_badges	3
has_contributing	yes
has_issue_template	no
has_code_of_conduct	yes
readme_badge_services	coveralls.io, shields.io
has_pull_request_template	yes

Sustainability & Governance

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

77Good · 23% of overall

Maintainer resilience (bus factor)

77Good

How it's scored

36/54	Bus factor — 3 contributor(s) cover half of all commits
17.1/22.5	Commit distribution — top contributor authored 24% of commits
13.5/13.5	Contributor breadth — 20 contributors
10/10	OpenSSF Scorecard: Contributors — project has 4 contributing companies or organizations

Inputs used

bus_factor	3
contributors_sampled	20
top_contributor_share	0.241

Issue & PR responsiveness

59Moderate

How it's scored

16.6/42	Issue resolution — 40% of issues closed
27.6/30	PR acceptance — 91/99 decided PRs merged
0/13	Newcomer PR acceptance — no first-time contributor's PR decided in 30d
7.5/15	OpenSSF Scorecard: Code-Review — Found 5/10 approved changesets -- score normalized to 5

Inputs used

merged_prs	91
open_issues	26
closed_issues	17
prs_merged_7d	0
prs_decided_7d	0
prs_merged_30d	2
prs_decided_30d	2
issue_closed_ratio	0.395
closed_unmerged_prs	8
first_time_authors_30d	0
first_time_prs_merged_30d	0
first_time_prs_decided_30d	0

Excluded from scoring (no data or not applicable): Newcomer PR acceptance. Remaining weights renormalized.

Ownership & stewardship

96Exceptional

How it's scored

30/30	Ownership backing — organization-owned
20/20	Verified domain
21/25	Owner reach — 820 followers of iotaledger
25/25	Track record — 108 public repos, account ~10 yr old

Inputs used

followers	820
owner_type	Organization
is_verified	yes
owner_login	iotaledger
public_repos	108
account_age_days	3,738

Engineering Quality

Are baseline engineering and documentation practices in place?

66Good · 19% of overall

Engineering practices

84Excellent

How it's scored

24/24	CI workflows — 7 workflow(s)
24/24	Tests present
16/16	Linter config — Cargo.toml ([workspace.lints]), iota_interaction/Cargo.toml ([lints]), iota_interaction_rust/Cargo.toml ([lints]), product_common/Cargo.toml ([lints]), rustfmt.toml
0/9.6	Pre-commit hooks
0/6.4	.editorconfig
20/20	OpenSSF Scorecard: CI-Tests — 10 out of 10 merged PRs checked by a CI test -- score normalized to 10

Inputs used

has_ci	yes
has_tests	yes
has_editorconfig	no
has_linter_config	yes
has_precommit_config	no

Documentation

40Weak

How it's scored

30/30	README
0/25	Documentation directory
0/15	Documentation / homepage site
0/10	Repository description
0/10	Topics
10/10	Wiki

Inputs used

topics	—
has_wiki	yes
homepage	—
docs_site	—
has_readme	yes
has_docs_dir	no
has_description	no

Security

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

60Moderate · 16% of overall

Security posture

50Moderate

How it's scored

7.5/7.5	Binary-Artifacts — no binaries found in the repo
0/7.5	Branch-Protection — branch protection not enabled on development/release branches
2.5/2.5	CI-Tests — 10 out of 10 merged PRs checked by a CI test -- score normalized to 10
0/2.5	CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
3.8/7.5	Code-Review — Found 5/10 approved changesets -- score normalized to 5
2.5/2.5	Contributors — project has 4 contributing companies or organizations
10/10	Dangerous-Workflow — no dangerous workflow patterns detected
7.5/7.5	Dependency-Update-Tool — update tool detected
0/5	Fuzzing — project is not fuzzed
2.5/2.5	License — license file detected
7.5/7.5	Maintained — 29 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
0/5	Packaging — no data
2.5/5	Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 5
0/5	SAST — SAST tool is not run on all commits -- score normalized to 0
0/5	Security-Policy — security policy file not detected
0/7.5	Signed-Releases — no data
0/7.5	Token-Permissions — detected GitHub workflow tokens with excessive permissions
0/7.5	Vulnerabilities — 10 existing vulnerabilities detected

Inputs used

source	openssf_scorecard
checks_evaluated	16
scorecard_version	v5.5.0
checks_inconclusive	2
scorecard_aggregate	5

Excluded from scoring (no data or not applicable): Packaging, Signed-Releases. Remaining weights renormalized.

Dependency advisories

100Exceptional

How it's scored

35/35	Direct dependencies free of known advisories — no direct dependency carries a known advisory
0/25	Indirect dependencies free of known advisories — transitive set not separable from development and test dependencies in this scope
0/40	No advisories left outstanding — no advisory carries a publication date

Inputs used

source	osv
advisories	10
affected_packages	4
assessed_packages	64
unassessed_packages	38
affected_by_severity	high 3, moderate 1
direct_affected_packages	0

Excluded from scoring (no data or not applicable): Indirect dependencies free of known advisories, No advisories left outstanding. Remaining weights renormalized. Matched 64 resolved dependencies against OSV. 38 could not be assessed — no resolved version, an unsupported ecosystem, or beyond the reported package list. This repository publishes no package the index resolves, so the repository dependency graph was assessed instead. That graph mixes development and test pins with shipped dependencies, so only the declared runtime dependencies are scored; transitive findings are reported as context and excluded from the score. 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

Agent context & guidance

32At Risk

How it's scored

0/45	Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15	Machine-readable docs (llms.txt)
32.5/40	Legible commit history — 61 of 100 human commits state their intent (structured subject or explanatory body)

Inputs used

has_llms_txt	no
llms_txt_url	—
legible_history_share	0.61
agent_instruction_files	—
agent_instruction_max_bytes	—

Verify loop (build / test / typecheck)

72Good

How it's scored

12.6/18	One-command bootstrap — Cargo.toml, bindings/wasm/iota_interaction_ts/Cargo.toml, iota_interaction/Cargo.toml (toolchain convention, no task runner)
22/22	Automated tests
11/11	Lint / format config — Cargo.toml ([workspace.lints]), iota_interaction/Cargo.toml ([lints]), iota_interaction_rust/Cargo.toml ([lints]), product_common/Cargo.toml ([lints]), rustfmt.toml
11/11	Static type checking — bindings/wasm/iota_interaction_ts/lib/tsconfig.json, bindings/wasm/iota_interaction_ts/tsconfig.json, bindings/wasm/tsconfig.json
10/10	Reproducible environment — lockfile
0/10	Demonstrated agent practice — no agent-authored commits among the last 100
0/8	Automated maintenance — no automated dependency updates observed
5/10	OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 5

Inputs used

has_nix	no
has_tests	yes
lockfiles	package-lock.json
has_dockerfile	no
typed_language	yes
bootstrap_files	—
has_devcontainer	no
has_linter_config	yes
typecheck_configs	bindings/wasm/iota_interaction_ts/lib/tsconfig.json, bindings/wasm/iota_interaction_ts/tsconfig.json, bindings/wasm/tsconfig.json
agent_commit_share	0
toolchain_manifests	Cargo.toml, bindings/wasm/iota_interaction_ts/Cargo.toml, iota_interaction/Cargo.toml, iota_interaction_rust/Cargo.toml, product_common/Cargo.toml
dependency_bot_commit_share	0

Code legibility for models

100Exceptional

How it's scored

45/45	Type-checkable code — Rust (statically typed)
55/55	Manageable file sizes — 0/82 source files over 60KB

Inputs used

primary_language	Rust
largest_source_bytes	34,726
source_files_sampled	82
oversized_source_files	0

Machine-readable interfaces

100Exceptional

How it's scored

0/40	API schema (OpenAPI/GraphQL/proto) — not applicable to this kind of software
0/20	MCP server — not applicable to this kind of software
40/40	Runnable examples — examples

Inputs used

example_dirs	examples
has_mcp_signal	no
api_schema_files	—
interfaces_expected_of	—

Excluded from scoring (no data or not applicable): API schema (OpenAPI/GraphQL/proto), MCP server. Remaining weights renormalized.

Key facts

0GitHub stars

20contributors

130commits, last 12 months

0days since last push

30releases

3bus factor

26open issues

crates.iopackage ecosystems

Data collection warnings

Could not fetch crates package 'product_common' from its registry
Could not fetch crates package 'iota_interaction' from its registry
Could not fetch crates package 'iota_interaction_rust' from its registry

More detail

Star and fork history 0 ★ / 2 ⇿

0Stars

2Forks

8Releases

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.

Major 0Minor 2Patch 6

OpenSSF Scorecard 5.0 / 10

5.0aggregate

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-19 06:13 UTC

10	Binary-Artifacts	no binaries found in the repo
0	Branch-Protection	branch protection not enabled on development/release branches
10	CI-Tests	10 out of 10 merged PRs checked by a CI test -- score normalized to 10
0	CII-Best-Practices	no effort to earn an OpenSSF best practices badge detected
5	Code-Review	Found 5/10 approved changesets -- score normalized to 5
10	Contributors	project has 4 contributing companies or organizations
10	Dangerous-Workflow	no dangerous workflow patterns detected
10	Dependency-Update-Tool	update tool detected
0	Fuzzing	project is not fuzzed
10	License	license file detected
10	Maintained	29 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
n/a	Packaging	packaging workflow not detected
5	Pinned-Dependencies	dependency not pinned by hash detected -- score normalized to 5
0	SAST	SAST tool is not run on all commits -- score normalized to 0
0	Security-Policy	security policy file not detected
n/a	Signed-Releases	no releases found
0	Token-Permissions	detected GitHub workflow tokens with excessive permissions
0	Vulnerabilities	10 existing vulnerabilities detected

Direct dependencies 40

Registry	Package	Version constraint	Manifest
crates.io	anyhow	`—`	iota_interaction/Cargo.toml
crates.io	async-trait	`0.1.81`	iota_interaction/Cargo.toml
crates.io	bcs	`—`	iota_interaction/Cargo.toml
crates.io	cfg-if	`—`	iota_interaction/Cargo.toml
crates.io	fastcrypto	`—`	iota_interaction/Cargo.toml
crates.io	iota-protocol-config	`—`	iota_interaction/Cargo.toml
crates.io	iota-sdk-crypto	`—`	iota_interaction/Cargo.toml
crates.io	iota-sdk-types	`—`	iota_interaction/Cargo.toml
crates.io	iota-types	`—`	iota_interaction/Cargo.toml
crates.io	jsonpath-rust	`0.5.1`	iota_interaction/Cargo.toml
crates.io	move-core-types	`—`	iota_interaction/Cargo.toml
crates.io	secret-storage	`—`	iota_interaction/Cargo.toml
crates.io	serde	`—`	iota_interaction/Cargo.toml
crates.io	serde_json	`—`	iota_interaction/Cargo.toml
crates.io	strum	`—`	iota_interaction/Cargo.toml
crates.io	thiserror	`—`	iota_interaction/Cargo.toml
crates.io	anyhow	`—`	iota_interaction_rust/Cargo.toml
crates.io	async-trait	`—`	iota_interaction_rust/Cargo.toml
crates.io	bcs	`—`	iota_interaction_rust/Cargo.toml
crates.io	iota-sdk-types	`—`	iota_interaction_rust/Cargo.toml
crates.io	secret-storage	`—`	iota_interaction_rust/Cargo.toml
crates.io	serde	`—`	iota_interaction_rust/Cargo.toml
crates.io	anyhow	`—`	product_common/Cargo.toml
crates.io	async-trait	`—`	product_common/Cargo.toml
crates.io	bcs	`—`	product_common/Cargo.toml
crates.io	cfg-if	`—`	product_common/Cargo.toml
crates.io	fastcrypto	`—`	product_common/Cargo.toml
crates.io	iota-keys	`—`	product_common/Cargo.toml
crates.io	iota-sdk-types	`—`	product_common/Cargo.toml
crates.io	itertools	`0.13.0`	product_common/Cargo.toml
crates.io	lazy_static	`1.5.0`	product_common/Cargo.toml
crates.io	phf	`—`	product_common/Cargo.toml
crates.io	reqwest	`0.13`	product_common/Cargo.toml
crates.io	secret-storage	`—`	product_common/Cargo.toml
crates.io	serde	`—`	product_common/Cargo.toml
crates.io	serde_json	`—`	product_common/Cargo.toml
crates.io	strum	`—`	product_common/Cargo.toml
crates.io	thiserror	`—`	product_common/Cargo.toml
crates.io	toml	`—`	product_common/Cargo.toml
crates.io	url	`2`	product_common/Cargo.toml

All dependencies 102

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

Registry	Package	Version	Relation
crates.io	anyhow	`—`	direct
crates.io	async-trait	`—`	direct
crates.io	itertools	`—`	direct
crates.io	jsonpath-rust	`—`	direct
crates.io	lazy_static	`—`	direct
crates.io	reqwest	`—`	direct
crates.io	serde	`—`	direct
crates.io	url	`—`	direct
crates.io	derive_more	`—`	indirect
crates.io	enum_dispatch	`—`	indirect
crates.io	eyre	`—`	indirect
crates.io	futures	`—`	indirect
crates.io	getrandom	`—`	indirect
crates.io	hex	`—`	indirect
crates.io	hyper	`—`	indirect
crates.io	iota-sdk	`—`	indirect
crates.io	iota_interaction	`—`	indirect
crates.io	iota_interaction_rust	`—`	indirect
crates.io	iota_interaction_ts	`—`	indirect
crates.io	js-sys	`—`	indirect
crates.io	js-sys	`0.3.85`	indirect
crates.io	json-proof-token	`—`	indirect
crates.io	jsonrpsee	`—`	indirect
crates.io	leb128	`—`	indirect
crates.io	nonempty	`—`	indirect
crates.io	primitive-types	`—`	indirect
crates.io	rand	`—`	indirect
crates.io	ref-cast	`—`	indirect
crates.io	schemars	`—`	indirect
crates.io	sd-jwt-payload	`—`	indirect
crates.io	serde-name	`—`	indirect
crates.io	serde-wasm-bindgen	`—`	indirect
crates.io	serde_repr	`—`	indirect
crates.io	serde_with	`—`	indirect
crates.io	tokio	`—`	indirect
crates.io	tracing	`—`	indirect
crates.io	uint	`—`	indirect
crates.io	wasm-bindgen	`—`	indirect
crates.io	wasm-bindgen-futures	`—`	indirect
npm	@0no-co/graphql.web	`1.0.13`	indirect
npm	@0no-co/graphqlsp	`1.12.16`	indirect
npm	@gql.tada/cli-utils	`1.6.3`	indirect
npm	@gql.tada/internal	`1.0.8`	indirect
npm	@graphql-typed-document-node/core	`3.2.0`	indirect
npm	@iota/bcs	`1.6.0`	indirect
npm	@iota/iota-sdk	`1.15.0`	indirect
npm	@isaacs/cliui	`8.0.2`	indirect
npm	@noble/curves	`1.8.1`	indirect
npm	@noble/hashes	`1.7.1`	indirect
npm	@scure/base	`1.2.4`	indirect
npm	@scure/bip32	`1.6.2`	indirect
npm	@scure/bip39	`1.5.4`	indirect
npm	@types/node	`22.10.1`	indirect
npm	ansi-regex	`5.0.1`	indirect
npm	ansi-regex	`6.1.0`	indirect
npm	ansi-styles	`4.3.0`	indirect
npm	ansi-styles	`6.2.1`	indirect
npm	balanced-match	`1.0.2`	indirect
npm	bignumber.js	`9.3.1`	indirect
npm	brace-expansion	`2.0.1`	indirect
npm	buffer-crc32	`0.2.13`	indirect
npm	color-convert	`2.0.1`	indirect
npm	color-name	`1.1.4`	indirect
npm	cross-spawn	`7.0.6`	indirect
npm	dprint	`0.33.0`	indirect
npm	eastasianwidth	`0.2.0`	indirect
npm	emoji-regex	`8.0.0`	indirect
npm	emoji-regex	`9.2.2`	indirect
npm	fd-slicer	`1.1.0`	indirect
npm	foreground-child	`3.3.1`	indirect
npm	glob	`11.0.1`	indirect
npm	gql.tada	`1.8.10`	indirect
npm	graphql	`16.10.0`	indirect
npm	is-fullwidth-code-point	`3.0.0`	indirect
npm	isexe	`2.0.0`	indirect
npm	jackspeak	`4.1.0`	indirect
npm	json5	`2.2.3`	indirect
npm	lru-cache	`11.0.2`	indirect
npm	minimatch	`10.0.1`	indirect
npm	minimist	`1.2.8`	indirect
npm	minipass	`7.1.2`	indirect
npm	package-json-from-dist	`1.0.1`	indirect
npm	path-key	`3.1.1`	indirect
npm	path-scurry	`2.0.0`	indirect
npm	pend	`1.2.0`	indirect
npm	rimraf	`6.0.1`	indirect
npm	shebang-command	`2.0.0`	indirect
npm	shebang-regex	`3.0.0`	indirect
npm	signal-exit	`4.1.0`	indirect
npm	string-width	`4.2.3`	indirect
npm	string-width	`5.1.2`	indirect
npm	strip-ansi	`6.0.1`	indirect
npm	strip-ansi	`7.1.0`	indirect
npm	strip-bom	`3.0.0`	indirect
npm	tsconfig-paths	`4.2.0`	indirect
npm	typescript	`5.7.3`	indirect
npm	undici-types	`6.20.0`	indirect
npm	valibot	`1.2.0`	indirect
npm	which	`2.0.2`	indirect
npm	wrap-ansi	`7.0.0`	indirect
npm	wrap-ansi	`8.1.0`	indirect
npm	yauzl	`2.10.0`	indirect

Dependency advisories 4

This repository publishes no package the index resolves, so its own dependency graph was assessed — 64 packages, which also include development and test pins that never ship: 4 carry known advisories, of which 0 are direct. 38 could not be assessed — no resolved version, an unsupported ecosystem, or beyond the reported package list.

Package	Version	Relation	Severity	Advisories	Fixed in
brace-expansion	`2.0.1`	indirect	high	5	`5.0.9`
glob	`11.0.1`	indirect	high	1	`11.1.0`
minimatch	`10.0.1`	indirect	high	3	`10.2.3`
valibot	`1.2.0`	indirect	moderate	1	`1.4.2`

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.

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.

Software health index

Score profile

Ownership

Metrics by category

Key facts

Data collection warnings

More detail

Feedback

Related records