Public record
Software health reportschema 0.16.0 · metrics 2.10.0 · 2026-07-20 19:57 UTC

metanorma / metanorma-jis

Metanorma for JIS

XSLT · Ruby · SCSSBSD-2-Clause★ 0 stars⑂ 0 forkssince Mar 2023View on GitHub ↗

metanorma/metanorma-jis holds a health index of 84 out of 100, placing it in the Excellent band. It scores highest on Vitality (100/100) and lowest on AI Readiness (28/100). It was last updated today. 2 contributors account for most of its recent work.

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

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

Ownership

MetanormaOrganization
94 followers330 public repossince May 2018

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
RubyGemsmetanorma-jis1.1.5-770 days ago

Metrics by category

Vitality

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

100Exceptional · 21% of overall

Development activity

100Exceptional
How it's scored
36/36Push recencylast push 0 days ago
36/36Commit cadence52/52 weeks with commits
18/18Commit volume337 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_year337
human_commit_share
days_since_last_push0
active_weeks_last_year52

Release discipline

100Exceptional
How it's scored
27/27Ships releases75 releases published
36/36Release recencylatest release 0 days ago
27/27Release cadencea release every ~14 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count75
latest_release_tagv1.1.5
releases_from_tagsno
days_since_latest_release0
mean_days_between_releases14
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?

50Moderate · 17% of overall
How it's scored
0/60Stars0 stars
0/25Forks0 forks
4.7/15Watchers8 watchers
Inputs used
forks0
stars0
watchers8
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history

Community health

92Excellent
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized license (BSD-2-Clause)
18/18CONTRIBUTING guide
13.5/13.5Code of conduct
0/7.2Issue template
6.3/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges
has_contributingyes
has_issue_templateno
has_code_of_conductyes
readme_badge_services
has_pull_request_templateyes
How it's scored
50.8/80Total downloads76,793 downloads all-time across rubygems
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packagesmetanorma-jis
dependents
ecosystemsrubygems
total_downloads76,793
monthly_downloads
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?

79Good · 23% of overall
How it's scored
25.2/54Bus factor2 contributor(s) cover half of all commits
11.9/22.5Commit distributiontop contributor authored 47% of commits
6.8/13.5Contributor breadth5 contributors
10/10OpenSSF Scorecard: Contributorsproject has 4 contributing companies or organizations
Inputs used
bus_factor2
contributors_sampled5
top_contributor_share0.473
How it's scored
38/42Issue resolution90% of issues closed
29.8/30PR acceptance367/370 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
7.5/15OpenSSF Scorecard: Code-ReviewFound 10/17 approved changesets -- score normalized to 5
Inputs used
merged_prs367
open_issues10
closed_issues95
prs_merged_7d
prs_decided_7d
prs_merged_30d
prs_decided_30d
issue_closed_ratio0.905
closed_unmerged_prs3
first_time_authors_30d
first_time_prs_merged_30d
first_time_prs_decided_30d
Excluded from scoring (no data or not applicable): Newcomer PR acceptance. Remaining weights renormalized.
How it's scored
30/30Ownership backingorganization-owned
0/20Verified domainverified-domain status not read for this organization
14.2/25Owner reach94 followers of metanorma
25/25Track record330 public repos, account ~8 yr old
Inputs used
followers94
owner_typeOrganization
is_verified
owner_loginmetanorma
public_repos330
account_age_days2,986
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable1 package(s) on rubygems
35/35Publish recencylatest publish 0 days ago
20/20Version history77 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagesmetanorma-jis
ecosystemsrubygems
any_deprecatedno
min_days_since_publish0

Engineering Quality

Are baseline engineering and documentation practices in place?

70Good · 19% of overall
How it's scored
24/24CI workflows3 workflow(s)
24/24Tests present
16/16Linter config.rubocop.yml
0/9.6Pre-commit hooks
0/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests13 out of 13 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

50Moderate
How it's scored
30/30README
0/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
0/10Topics
10/10Wiki
Inputs used
topics
has_wikiyes
homepage
docs_site
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

53Moderate · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
0/7.5Branch-Protectionbranch protection not enabled on development/release branches
2.5/2.5CI-Tests13 out of 13 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
3.8/7.5Code-ReviewFound 10/17 approved changesets -- score normalized to 5
2.5/2.5Contributorsproject has 4 contributing companies or organizations
10/10Dangerous-Workflowno dangerous workflow patterns detected
0/7.5Dependency-Update-Toolno update 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
0/5Packagingno data
0/5Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
5/5SASTSAST tool is run on all commits
0/5Security-Policysecurity policy file not detected
0/7.5Signed-Releasesno data
0/7.5Token-Permissionsdetected GitHub workflow tokens with excessive permissions
7.5/7.5Vulnerabilities0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate5.3
Excluded from scoring (no data or not applicable): Packaging, 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.

28At Risk · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
0/40Legible commit historyno data
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share
agent_instruction_files
agent_instruction_max_bytes
Excluded from scoring (no data or not applicable): Legible commit history. Remaining weights renormalized.
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format config.rubocop.yml
0/11Static type checking
0/10Reproducible environment
0/10Demonstrated agent practiceno data
0/8Automated maintenanceno data
0/10OpenSSF Scorecard: Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsyes
lockfiles
has_dockerfileno
typed_languageno
bootstrap_files
has_devcontainerno
has_linter_configyes
typecheck_configs
agent_commit_share
toolchain_manifests
dependency_bot_commit_share
Excluded from scoring (no data or not applicable): Demonstrated agent practice, Automated maintenance. Remaining weights renormalized.
How it's scored
0/45Type-checkable codeXSLT without a type-check config
48.9/55Manageable file sizes5/45 source files over 60KB
Inputs used
primary_languageXSLT
largest_source_bytes94,994
source_files_sampled45
oversized_source_files5

Key facts

0GitHub stars
5contributors
337commits, last 12 months
0days since last push
75releases
2bus factor
10open issues
RubyGemspackage ecosystems

Data collection warnings

  • No resolved dependencies carried a version and a supported ecosystem

More detail

OpenSSF Scorecard 5.3 / 10
5.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-07-20 19:56 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
10CI-Tests13 out of 13 merged PRs checked by a CI test -- score normalized to 10
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
5Code-ReviewFound 10/17 approved changesets -- score normalized to 5
10Contributorsproject has 4 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
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
0Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
10SASTSAST tool is run on all commits
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
10Vulnerabilities0 existing vulnerabilities detected
All dependencies 18

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

RegistryPackageVersionRelation
RubyGemscanonindirect
RubyGemsdebugindirect
RubyGemsequivalent-xmlindirect
RubyGemsguardindirect
RubyGemsguard-rspecindirect
RubyGemsievindirect
RubyGemsjapanese_calendarindirect
RubyGemsmetanorma-isoindirect
RubyGemsopensslindirect
RubyGemspubidindirect
RubyGemsrakeindirect
RubyGemsrspecindirect
RubyGemsrubocopindirect
RubyGemsrubocop-performanceindirect
RubyGemssassc-embeddedindirect
RubyGemssimplecovindirect
RubyGemstimecopindirect
RubyGemswebmockindirect
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.16.0 — full methodology · metrics wiki.

How one result sits in the wider record: aggregate statisticsRubyGems.