Public record
Software health reportschema 0.27.0 · metrics 2.10.0 · 2026-08-01 15:45 UTC

barakugav / jix

Multi-dimensional array library with block-compressed storage and lazy-evaluated operations

Rust · PythonApache-2.0★ 3 stars⑂ 0 forkssince Mar 2026View on GitHub ↗

barakugav/jix holds a health index of 69 out of 100, placing it in the Good band. It scores highest on Vitality (86/100) and lowest on Community & Adoption (34/100). It was last updated today. A single contributor accounts for most of its recent work.

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

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

Ownership

Barak UgavPersonal account
16 followers22 public repossince Oct 2015

This repository is owned by a personal account. A single-owner project carries more continuity risk than an organization-backed one.

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
crates.iojix0.0.41840 days agocompressionndarrayzstddata-structuresscience
crates.iojix-macros0.0.43140 days agocompressionndarrayzstddata-structuresscience
PyPIjix0.0.42,17350 days agondarraycompressionzstd

Metrics by category

Vitality

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

86Excellent · 21% of overall
How it's scored
36/36Push recencylast push 0 days ago
11.8/36Commit cadence17/52 weeks with commits
18/18Commit volume195 commits in the last year
10/10OpenSSF Scorecard: Maintained30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year195
human_commit_share0.95
days_since_last_push0
active_weeks_last_year17

Release discipline

100Exceptional
How it's scored
27/27Ships releases3 releases published
36/36Release recencylatest release 35 days ago
27/27Release cadencea release every ~0.1 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count3
latest_release_tagv0.0.3
releases_from_tagsno
days_since_latest_release35
mean_days_between_releases0.1
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?

34At Risk · 17% of overall
How it's scored
4.9/60Stars3 stars
0/25Forks0 forks
0/15Watchers0 watchers
Inputs used
forks0
stars3
watchers0
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized license (Apache-2.0)
0/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_services
has_pull_request_templateno
How it's scored
44.6/80Monthly downloads2,222 downloads/month across crates, pypi
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packagesjix, jix-macros, jix
dependents
ecosystemscrates, pypi
total_downloads147
monthly_downloads2,222
unverified_packages_excluded
Excluded from scoring (no data or not applicable): Registry dependents. Remaining weights renormalized.

Sustainability & Governance

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

50Moderate · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
0/22.5Commit distributiontop contributor authored 100% of commits
1.4/13.5Contributor breadth1 contributors
0/10OpenSSF Scorecard: Contributorsproject has 0 contributing companies or organizations -- score normalized to 0
Inputs used
bus_factor1
contributors_sampled1
top_contributor_share1
How it's scored
0/42Issue resolutionno issues or no data
26.1/30PR acceptance33/38 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-ReviewFound 0/25 approved changesets -- score normalized to 0
Inputs used
merged_prs33
open_issues0
closed_issues0
prs_merged_7d
prs_decided_7d
prs_merged_30d
prs_decided_30d
issue_closed_ratio
closed_unmerged_prs5
first_time_authors_30d
first_time_prs_merged_30d
first_time_prs_decided_30d
Excluded from scoring (no data or not applicable): Issue resolution, Newcomer PR acceptance. Remaining weights renormalized.
How it's scored
10/30Ownership backingpersonal (user) account
0/20Verified domainnot applicable to user accounts
8.8/25Owner reach16 followers of barakugav
21.9/25Track record22 public repos, account ~10 yr old
Inputs used
followers16
owner_typeUser
is_verified
owner_loginbarakugav
public_repos22
account_age_days3,929
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable3 package(s) on crates, pypi
35/35Publish recencylatest publish 0 days ago
20/20Version history5 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagesjix, jix-macros, jix
ecosystemscrates, pypi
any_deprecatedno
min_days_since_publish0

Engineering Quality

Are baseline engineering and documentation practices in place?

86Excellent · 19% of overall
How it's scored
24/24CI workflows4 workflow(s)
24/24Tests present
16/16Linter config.ruff.toml
0/9.6Pre-commit hooks
0/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests27 out of 27 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

90Excellent
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage sitehttps://docs.rs/jix
10/10Repository description
10/10Topics4 topics
0/10Wiki
Inputs used
topicscompression, ndarray, rust, python
has_wikino
homepage
docs_sitehttps://docs.rs/jix
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

50Moderate · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
0/7.5Branch-Protectionno data
2.5/2.5CI-Tests27 out of 27 merged PRs checked by a CI test -- score normalized to 10
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0/7.5Code-ReviewFound 0/25 approved changesets -- score normalized to 0
0/2.5Contributorsproject has 0 contributing companies or organizations -- score normalized to 0
10/10Dangerous-Workflowno dangerous workflow patterns detected
7.5/7.5Dependency-Update-Toolupdate tool detected
0/5Fuzzingproject is not fuzzed
2.5/2.5Licenselicense file detected
7.5/7.5Maintained30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
5/5Packagingpackaging workflow detected
0/5Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
0/5SASTSAST tool is not run on all commits -- score normalized to 0
0/5Security-Policysecurity policy file not detected
0/7.5Signed-Releasesno data
0/7.5Token-Permissionsdetected GitHub workflow tokens with excessive permissions
2.2/7.5Vulnerabilities7 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate5
Excluded from scoring (no data or not applicable): Branch-Protection, Signed-Releases. 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.

70Good · 4% of overall
How it's scored
45/45Agent instructionsCLAUDE.md
0/15Machine-readable docs (llms.txt)
15.2/40Legible commit history27 of 95 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share0.284
agent_instruction_filesCLAUDE.md
agent_instruction_max_bytes10,115
How it's scored
12.6/18One-command bootstrapjix-macros/Cargo.toml, jix-py/Cargo.toml, jix/Cargo.toml (toolchain convention, no task runner)
22/22Automated tests
11/11Lint / format config.ruff.toml
11/11Static type checkingRust (statically typed)
10/10Reproducible environmentlockfile
0/10Demonstrated agent practiceno agent-authored commits among the last 100
8/8Automated maintenance5 of the last 100 commits are automated dependency updates
0/10OpenSSF Scorecard: Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsyes
lockfilesCargo.lock
has_dockerfileno
typed_languageyes
bootstrap_files
has_devcontainerno
has_linter_configyes
typecheck_configs
agent_commit_share0
toolchain_manifestsjix-macros/Cargo.toml, jix-py/Cargo.toml, jix/Cargo.toml, jix/schema/Cargo.toml
dependency_bot_commit_share0.05
How it's scored
45/45Type-checkable codeRust (statically typed)
53.9/55Manageable file sizes3/153 source files over 60KB
Inputs used
primary_languageRust
largest_source_bytes140,844
source_files_sampled153
oversized_source_files3
How it's scored
40/40API schema (OpenAPI/GraphQL/proto)jix/schema/proto/jix/v1/array.proto, jix/schema/proto/jix/v1/block.proto, jix/schema/proto/jix/v1/codec.proto, jix/schema/proto/jix/v1/dtype.proto, jix/schema/proto/jix/v1/structure.proto
0/20MCP servernot applicable to this kind of software
0/40Runnable examples
Inputs used
example_dirs
has_mcp_signalno
api_schema_filesjix/schema/proto/jix/v1/array.proto, jix/schema/proto/jix/v1/block.proto, jix/schema/proto/jix/v1/codec.proto, jix/schema/proto/jix/v1/dtype.proto, jix/schema/proto/jix/v1/structure.proto
interfaces_expected_of
Excluded from scoring (no data or not applicable): MCP server. Remaining weights renormalized.

Key facts

3GitHub stars
1contributors
195commits, last 12 months
0days since last push
3releases
1bus factor
0open issues
crates.io, PyPIpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • Could not fetch crates package 'jix-python' from its registry
  • GitHub dependency-graph SBOM unavailable (404); the dependency graph may be disabled for this repository
  • deps.dev does not index crates:jix@0.0.4; advisories assessed against the repository dependency graph instead

More detail

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-08-01 15:44 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
10CI-Tests27 out of 27 merged PRs checked by a CI test -- score normalized to 10
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0Code-ReviewFound 0/25 approved changesets -- score normalized to 0
0Contributorsproject has 0 contributing companies or organizations -- score normalized to 0
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate 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
10Packagingpackaging workflow 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
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
3Vulnerabilities7 existing vulnerabilities detected
Direct dependencies 20
RegistryPackageVersion constraintManifest
crates.iosyn3.0jix-macros/Cargo.toml
crates.ioquote1.0jix-macros/Cargo.toml
crates.ioproc-macro-crate3.5jix-macros/Cargo.toml
crates.iopyo30.29jix-py/Cargo.toml
crates.iojix_core=0.0.4jix-py/Cargo.toml
crates.ionumpy0.29jix-py/Cargo.toml
crates.ionum-traits0.2jix-py/Cargo.toml
crates.iopyo3-stub-gen0.23.0jix-py/Cargo.toml
crates.ioarrayvec0.7jix-py/Cargo.toml
crates.iondarray0.17.0jix-py/Cargo.toml
PyPInumpy~=2.0jix-py/pyproject.toml
crates.iojix-macros=0.0.4jix/Cargo.toml
crates.iondarray>=0.16,<0.18jix/Cargo.toml
crates.iomemmap20.9jix/Cargo.toml
crates.ionum-traits0.2jix/Cargo.toml
crates.iozstd0.13jix/Cargo.toml
crates.ioprost0.14jix/Cargo.toml
crates.iohalf2jix/Cargo.toml
crates.ionum-complex0.4jix/Cargo.toml
crates.iomultiversion0.8.0jix/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.27.0 — full methodology · metrics wiki.

How one result sits in the wider record: aggregate statisticscrates.io, PyPI.