Public record
Software health reportschema 0.11.0 · metrics 2.10.0 · 2026-07-15 14:34 UTC

zakodium-oss / react-ocl-nmr

JavaScriptMIT★ 0 stars⑂ 2 forkssince May 2020View on GitHub ↗

zakodium-oss/react-ocl-nmr holds a health index of 38 out of 100, placing it in the Weak band. It scores highest on Sustainability & Governance (63/100) and lowest on AI Readiness (28/100). It was last updated 320 days ago. A single contributor accounts for most of its recent work.

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

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

Ownership

9 followers20 public repossince Mar 2022

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
npmreact-ocl-nmr4.1.14,57428320 days ago

Metrics by category

Vitality

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

35Weak · 21% of overall
How it's scored
3.6/36Push recencylast push 320 days ago
0.7/36Commit cadence1/52 weeks with commits
7/18Commit volume5 commits in the last year
0/10OpenSSF Scorecard: Maintained0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Inputs used
commits_last_year5
human_commit_share
days_since_last_push320
active_weeks_last_year1
How it's scored
27/27Ships releases19 releases published
16.2/36Release recencylatest release 320 days ago
19.8/27Release cadencea release every ~84 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count19
latest_release_tagv4.1.1
releases_from_tagsno
days_since_latest_release320
mean_days_between_releases84
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
0/60Stars0 stars
0/25Forks2 forks
1.7/15Watchers3 watchers
Inputs used
forks2
stars0
watchers3
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized license (MIT)
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
48.8/80Monthly downloads4,574 downloads/month across npm
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packagesreact-ocl-nmr
dependents
ecosystemsnpm
total_downloads
monthly_downloads4,574
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?

63Moderate · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
10.8/22.5Commit distributiontop contributor authored 52% of commits
8.1/13.5Contributor breadth6 contributors
10/10OpenSSF Scorecard: Contributorsproject has 16 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled6
top_contributor_share0.518
How it's scored
21/42Issue resolution50% of issues closed
30/30PR acceptance27/27 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
6/15OpenSSF Scorecard: Code-ReviewFound 14/30 approved changesets -- score normalized to 4
Inputs used
merged_prs27
open_issues5
closed_issues5
prs_merged_7d
prs_decided_7d
prs_merged_30d
prs_decided_30d
issue_closed_ratio0.5
closed_unmerged_prs0
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
7.2/25Owner reach9 followers of zakodium-oss
18.3/25Track record20 public repos, account ~4 yr old
Inputs used
followers9
owner_typeOrganization
is_verified
owner_loginzakodium-oss
public_repos20
account_age_days1,580
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.
How it's scored
25/25Published & resolvable1 package(s) on npm
26/35Publish recencylatest publish 320 days ago
20/20Version history28 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagesreact-ocl-nmr
ecosystemsnpm
any_deprecatedno
min_days_since_publish320

Engineering Quality

Are baseline engineering and documentation practices in place?

36Weak · 19% of overall
How it's scored
24/24CI workflows1 workflow(s)
0/24Tests present
16/16Linter configeslint.config.js
0/9.6Pre-commit hooks
0/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Tests0 out of 17 merged PRs checked by a CI test -- score normalized to 0
Inputs used
has_ciyes
has_testsno
has_editorconfigno
has_linter_configyes
has_precommit_configno

Documentation

30At Risk
How it's scored
30/30README
0/25Documentation directory
0/15Documentation / homepage site
0/10Repository description
0/10Topics
0/10Wiki
Inputs used
topics
has_wikino
homepage
docs_site
has_readmeyes
has_docs_dirno
has_descriptionno

Security

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

39Weak · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
0/7.5Branch-Protectionno data
0/2.5CI-Tests0 out of 17 merged PRs checked by a CI test -- score normalized to 0
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
3/7.5Code-ReviewFound 14/30 approved changesets -- score normalized to 4
2.5/2.5Contributorsproject has 16 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
0/7.5Maintained0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
0/5Packagingno data
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
7.5/7.5Vulnerabilities0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated15
scorecard_versionv5.5.0
checks_inconclusive3
scorecard_aggregate3.9
Excluded from scoring (no data or not applicable): Branch-Protection, 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
0/22Automated tests
11/11Lint / format configeslint.config.js
11/11Static type checkingtsconfig.json
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_testsno
lockfiles
has_dockerfileno
typed_languageno
bootstrap_files
has_devcontainerno
has_linter_configyes
typecheck_configstsconfig.json
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
27/45Type-checkable codeJavaScript with type-check config (tsconfig.json)
55/55Manageable file sizes0/9 source files over 60KB
Inputs used
primary_languageJavaScript
largest_source_bytes35,770
source_files_sampled9
oversized_source_files0

Key facts

0GitHub stars
6contributors
5commits, last 12 months
320days since last push
19releases
1bus factor
5open issues
npmpackage ecosystems

More detail

OpenSSF Scorecard 3.9 / 10
3.9aggregate

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-15 14:34 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
0CI-Tests0 out of 17 merged PRs checked by a CI test -- score normalized to 0
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
4Code-ReviewFound 14/30 approved changesets -- score normalized to 4
10Contributorsproject has 16 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
0Maintained0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
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
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 3
RegistryPackageVersion constraintManifest
npmopenchemlib^9.1.1package.json
npmopenchemlib-utils^8.1.1package.json
npmreact-ocl^8.2.0package.json
All dependencies 16

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

RegistryPackageVersionRelation
npmopenchemlib^9.1.1direct
npmopenchemlib-utils^8.1.1direct
npmreact-ocl^8.2.0direct
npm@types/react^18.3.11indirect
npm@types/react-dom^18.3.1indirect
npm@vitejs/plugin-react^4.4.1indirect
npmeslint^9.26.0indirect
npmeslint-config-zakodium^15.0.1indirect
npmpostcss^8.5.3indirect
npmprettier^3.5.3indirect
npmreact^18.3.1indirect
npmreact-dom^18.3.1indirect
npmrimraf^6.0.1indirect
npmtailwindcss^3.4.14indirect
npmtypescript^5.8.3indirect
npmvite^6.3.5indirect
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.11.0 — full methodology · metrics wiki.

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