Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-24 06:07 UTC

volt-hq / iroh-ffi

Volt fork of n0-computer/iroh-ffi — repackaged Swift xcframework with iOS 17.x deployment targets. Upstream code MIT OR Apache-2.0.

Kotlin · C · SwiftApache-2.0★ 0 stars⑂ 0 forkssince Jul 2026forkView on GitHub ↗
KindLibraryApplicationhow this is determined

volt-hq/iroh-ffi holds a health index of 42 out of 100, placing it in the Weak band. It scores highest on AI Readiness (72/100) and lowest on Community & Adoption (12/100). It was last updated 8 days ago. 2 contributors account for most of its recent work.

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

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

Ownership

VoltOrganization
0 followers4 public repossince Jul 2026

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
PyPIirohpoints to another repo — not scored1.1.017,1933469 days ago—
npm@number0/irohpoints to another repo — not scored1.1.028,6831769 days agoirohdistributedapplicationsp2ppeer-to-peernetworkingnetworkprotocol

Metrics by category

Vitality

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

62Moderate · 21% of overall

Development activity

43Weak
How it's scored
28.8/36Push recency — last push 8 days ago
2.8/36Commit cadence — 4/52 weeks with commits
11.7/18Commit volume — 19 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_year19
human_commit_share0.99
days_since_last_push8
active_weeks_last_year4

Release discipline

90Excellent
How it's scored
27/27Ships releases — 6 releases published
36/36Release recency — latest release 14 days ago
27/27Release cadence — a release every ~14.2 days
0/10OpenSSF Scorecard: Signed-Releases — Project has not signed or included provenance with any releases.
Inputs used
releases_count6
latest_release_tagv1.1.1-volt.3
releases_from_tagsno
days_since_latest_release14
mean_days_between_releases14.2

Community & Adoption

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

12Critical · 17% of overall

Popularity & adoption

1Critical
How it's scored
0/60Stars — 0 stars
0/25Forks — 0 forks
0/15Watchers — 0 watchers
Inputs used
forks0
stars0
watchers0
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history

Community health

25At Risk
How it's scored
0/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_readmeno
has_licenseno
readme_badges2
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?

51Moderate · 23% of overall

Maintainer resilience (bus factor)

64Moderate
How it's scored
25.2/54Bus factor — 2 contributor(s) cover half of all commits
15.1/22.5Commit distribution — top contributor authored 33% of commits
13.5/13.5Contributor breadth — 14 contributors
10/10OpenSSF Scorecard: Contributors — project has 24 contributing companies or organizations
Inputs used
bus_factor2
contributors_sampled14
top_contributor_share0.327

Issue & PR responsiveness

49Weak
How it's scored
0/42Issue resolution — no issues or no data
20/30PR acceptance — 2/3 decided PRs merged
8.7/13Newcomer PR acceptance — 2/3 first-time contributors' PRs merged in 30d
0/15OpenSSF Scorecard: Code-Review — Found 0/30 approved changesets -- score normalized to 0
Inputs used
merged_prs2
open_issues0
closed_issues0
prs_merged_7d0
prs_decided_7d0
prs_merged_30d2
prs_decided_30d3
issue_closed_ratio—
closed_unmerged_prs1
first_time_authors_30d1
first_time_prs_merged_30d2
first_time_prs_decided_30d3
Excluded from scoring (no data or not applicable): Issue resolution. Remaining weights renormalized.

Ownership & stewardship

36Weak
How it's scored
30/30Ownership backing — organization-owned
0/20Verified domain
0/25Owner reach — 0 followers of volt-hq
5.5/25Track record — 4 public repos, account ~0 yr old
Inputs used
followers0
owner_typeOrganization
is_verifiedno
owner_loginvolt-hq
public_repos4
account_age_days70

Engineering Quality

Are baseline engineering and documentation practices in place?

58Moderate · 19% of overall

Engineering practices

80Excellent
How it's scored
24/24CI workflows — 8 workflow(s)
24/24Tests present
16/16Linter config — rustfmt.toml
0/9.6Pre-commit hooks
0/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Tests — no data
Inputs used
has_ciyes
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.

Documentation

25At Risk
How it's scored
0/30README
0/25Documentation directory
15/15Documentation / homepage site — https://iroh.computer
0/10Repository description
0/10Topics
10/10Wiki
Inputs used
topics—
has_wikiyes
homepagehttps://iroh.computer
docs_sitehttps://iroh.computer
has_readmeno
has_docs_dirno
has_descriptionno

Security

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

26At Risk · 16% of overall

Security posture

26At Risk
How it's scored
6.8/7.5Binary-Artifacts — binaries present in source code
0/7.5Branch-Protection — branch protection not enabled on development/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 24 contributing companies or organizations
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/5Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
0/5SAST — no SAST tool detected
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
0/7.5Vulnerabilities — 20 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated17
scorecard_versionv5.5.0
checks_inconclusive1
scorecard_aggregate2.6
Excluded from scoring (no data or not applicable): CI-Tests. 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.

72Good · 4% of overall

Agent context & guidance

55Moderate
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
15/15Machine-readable docs (llms.txt) — llms.txt served by the project website (https://iroh.computer/llms.txt)
40/40Legible commit history — 96 of 99 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtyes
llms_txt_urlhttps://iroh.computer/llms.txt
legible_history_share0.97
agent_instruction_files—
agent_instruction_max_bytes—

Verify loop (build / test / typecheck)

77Good
How it's scored
12.6/18One-command bootstrap — Cargo.toml, iroh-js/Cargo.toml, kotlin/lib/build.gradle.kts (toolchain convention, no task runner)
22/22Automated tests
11/11Lint / format config — rustfmt.toml
11/11Static type checking — iroh-js/tsconfig.json
10/10Reproducible environment — lockfile
2/10Demonstrated agent practice — 1 of the last 100 commits agent-authored or agent-credited
8/8Automated maintenance — 1 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_testsyes
lockfilesCargo.lock, yarn.lock
has_dockerfileno
typed_languageyes
bootstrap_files—
has_devcontainerno
has_linter_configyes
typecheck_configsiroh-js/tsconfig.json
agent_commit_share0.01
toolchain_manifestsCargo.toml, iroh-js/Cargo.toml, kotlin/lib/build.gradle.kts
dependency_bot_commit_share0.01

Code legibility for models

94Exceptional
How it's scored
45/45Type-checkable code — Kotlin (statically typed)
48.9/55Manageable file sizes — 6/54 source files over 60KB
Inputs used
primary_languageKotlin
largest_source_bytes2,752,818
source_files_sampled54
oversized_source_files6

Key facts

0GitHub stars
14contributors
19commits, last 12 months
8days since last push
6releases
2bus factor
0open issues
crates.io, npm, PyPIpackage ecosystems

Data collection warnings

  • Community profile unavailable
  • Could not fetch crates package 'iroh-ffi' from its registry
  • pypi package 'iroh' points at a different repository (https://iroh.computer); excluded from ecosystem scoring
  • Could not fetch crates package 'number0_iroh' from its registry
  • npm package '@number0/iroh' points at a different repository (https://github.com/n0-computer/iroh-ffi); excluded from ecosystem scoring
  • GitHub dependency-graph SBOM unavailable (404); the dependency graph may be disabled for this repository

More detail

OpenSSF Scorecard 2.6 / 10
2.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-24 06:07 UTC

9Binary-Artifactsbinaries present in source code
0Branch-Protectionbranch protection not enabled on development/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 24 contributing companies or organizations
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
0Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
0SASTno SAST tool detected
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
0Vulnerabilities20 existing vulnerabilities detected
Direct dependencies 32
RegistryPackageVersion constraintManifest
crates.ioanyhow1.0.69Cargo.toml
crates.ioasync-trait0.1.80Cargo.toml
crates.ioiroh1.0.0Cargo.toml
crates.ioiroh-base1.0.0Cargo.toml
crates.ioiroh-metrics1.0.0Cargo.toml
crates.ioiroh-relay1.0.0Cargo.toml
crates.ioiroh-services1.0.0Cargo.toml
crates.ioiroh-tickets1.0.0Cargo.toml
crates.ion0-error1.0.0Cargo.toml
crates.iothiserror2.0Cargo.toml
crates.iotokio1.25.0Cargo.toml
crates.iouniffi0.31.1Cargo.toml
crates.iourl2.4Cargo.toml
crates.iotracing0.1.40Cargo.toml
crates.iotracing-subscriber0.3.17Cargo.toml
crates.ioserde1.0.196Cargo.toml
crates.ioderive_more2.0Cargo.toml
crates.ion0-future0.3Cargo.toml
crates.ionapi3iroh-js/Cargo.toml
crates.ionapi-derive3iroh-js/Cargo.toml
crates.ioanyhow1.0.69iroh-js/Cargo.toml
crates.ioiroh1.0.0iroh-js/Cargo.toml
crates.ioiroh-base1.0.0iroh-js/Cargo.toml
crates.ioiroh-metrics1.0.0iroh-js/Cargo.toml
crates.ioiroh-relay1.0.0iroh-js/Cargo.toml
crates.ioiroh-services1.0.0iroh-js/Cargo.toml
crates.ioiroh-tickets1.0.0iroh-js/Cargo.toml
crates.ion0-future0.3iroh-js/Cargo.toml
crates.iotokio1.25.0iroh-js/Cargo.toml
crates.iourl2.4iroh-js/Cargo.toml
crates.iotracing0.1.40iroh-js/Cargo.toml
crates.iotracing-subscriber0.3.17iroh-js/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.

Related records

Inspected repositories sharing catalogue tags or ecosystems with volt-hq/iroh-ffi. Read them side by side →

100risingwavelabs/risingwaveEvent streaming platform for agentic AI. Continuously ingest, transform, and serve event streams in real time, at scale.Exceptional100microsoft/onnxruntimeONNX Runtime: cross-platform, high performance ML inferencing and training acceleratorExceptional99IBM/mcp-context-forgeAn AI Gateway, registry, and proxy that sits in front of any MCP, A2A, or REST/gRPC APIs, exposing a unified endpoint with centralized discovery, guardrails and management. Optimizes Agent & Tool calling, and supports plugins.Exceptional99taskforcesh/bullmqBullMQ - Message Queue and Batch processing for NodeJS, Python, .NET, Elixir, Rust and PHP based on Redis or PostgreSQLExceptional99microsoft/foundry-localExceptional99astral-sh/ruffAn extremely fast Python linter and code formatter, written in Rust.Exceptional

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 — PyPI, npm.