Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-10-01 16:16 UTC

zoho / react-native-zohodesk-portal-sdk

Kotlin · JavaScript · SwiftNo license detected★ 10 stars⑂ 7 forkssince Apr 2020View on GitHub ↗
KindLibraryMobile applicationhow this is determined

zoho/react-native-zohodesk-portal-sdk holds a health index of 42 out of 100, placing it in the Weak band. It scores highest on Sustainability & Governance (79/100) and lowest on Engineering Quality (23/100). It was last updated 35 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

ZohoOrganization · verified domain
815 followers258 public repossince Oct 2013

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
npm@zohocorp/zohodesk-portal-kb3.5.32,6542634 days agozohodesk
npm@zohocorp/zohodesk-portal-core3.5.31,7492634 days agozohodesk
npm@zohocorp/zohodesk-portal-apikit3.5.32,6532634 days agozohodesk
npm@zohocorp/zohodesk-portal-ticket3.5.32,3932634 days agozohodesk
npm@zohocorp/zohodesk-portal-chatkit3.5.31,5522634 days agozohodesk
npm@zohocorp/zohodesk-portal-salesiq3.5.31,8462634 days agozohodesk
npm@zohocorp/zohodesk-portal-community3.5.31,5602634 days agozohodesk
npm@zohocorp/zohodesk-portal-configuration3.5.32,2692634 days agozohodesk

Metrics by category

Vitality

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

50Moderate · 21% of overall
How it's scored
18/36Push recency — last push 35 days ago
11.1/36Commit cadence — 16/52 weeks with commits
15.8/18Commit volume — 57 commits in the last year
3/10OpenSSF Scorecard: Maintained — 4 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 3
Inputs used
commits_last_year57
human_commit_share1
days_since_last_push35
active_weeks_last_year16
How it's scored
27/27Ships releases — 1 releases published
7.2/36Release recency — latest release 696 days ago
12.6/27Release cadence — cadence unknown (single release)
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count1
latest_release_tagv2.0.1
releases_from_tagsno
days_since_latest_release696
mean_days_between_releases—
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?

27At Risk · 17% of overall
How it's scored
15.5/60Stars — 10 stars
6.5/25Forks — 7 forks
0/15Watchers — 2 watchers
Inputs used
forks7
stars10
watchers2
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
0/22.5README
0/22.5License — no license file detected
0/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeno
has_licenseno
readme_badges—
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_services—
has_pull_request_templateno
How it's scored
56.3/80Monthly downloads — 16,676 downloads/month across npm
0/20Registry dependents — not reported by this ecosystem
Inputs used
packages@zohocorp/zohodesk-portal-kb, @zohocorp/zohodesk-portal-core, @zohocorp/zohodesk-portal-apikit, @zohocorp/zohodesk-portal-ticket, @zohocorp/zohodesk-portal-chatkit, @zohocorp/zohodesk-portal-salesiq, @zohocorp/zohodesk-portal-community, @zohocorp/zohodesk-portal-configuration
dependents—
ecosystemsnpm
total_downloads—
monthly_downloads16,676
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 factor — 2 contributor(s) cover half of all commits
14.6/22.5Commit distribution — top contributor authored 35% of commits
10.8/13.5Contributor breadth — 8 contributors
0/10OpenSSF Scorecard: Contributors — project has 0 contributing companies or organizations -- score normalized to 0
Inputs used
bus_factor2
contributors_sampled8
top_contributor_share0.353
How it's scored
25.2/42Issue resolution — 60% of issues closed
29/30PR acceptance — 30/31 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
15/15OpenSSF Scorecard: Code-Review — all changesets reviewed
Inputs used
merged_prs30
open_issues10
closed_issues15
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio0.6
closed_unmerged_prs1
first_time_authors_30d0
first_time_prs_merged_30d0
first_time_prs_decided_30d0
Excluded from scoring (no data or not applicable): Newcomer PR acceptance. Remaining weights renormalized.
How it's scored
30/30Ownership backing — organization-owned
20/20Verified domain
20.9/25Owner reach — 815 followers of zoho
25/25Track record — 258 public repos, account ~13 yr old
Inputs used
followers815
owner_typeOrganization
is_verifiedyes
owner_loginzoho
public_repos258
account_age_days4,745

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 8 package(s) on npm
35/35Publish recency — latest publish 34 days ago
20/20Version history — 26 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packages@zohocorp/zohodesk-portal-kb, @zohocorp/zohodesk-portal-core, @zohocorp/zohodesk-portal-apikit, @zohocorp/zohodesk-portal-ticket, @zohocorp/zohodesk-portal-chatkit, @zohocorp/zohodesk-portal-salesiq, @zohocorp/zohodesk-portal-community, @zohocorp/zohodesk-portal-configuration
ecosystemsnpm
any_deprecatedno
min_days_since_publish34

Engineering Quality

Are baseline engineering and documentation practices in place?

23At Risk · 19% of overall
How it's scored
0/24CI workflows
0/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
6.4/6.4.editorconfig
16/20OpenSSF Scorecard: CI-Tests — 5 out of 6 merged PRs checked by a CI test -- score normalized to 8
Inputs used
has_cino
has_testsno
has_editorconfigyes
has_linter_configno
has_precommit_configno

Documentation

25At Risk
How it's scored
0/30README
0/25Documentation directory
15/15Documentation / homepage site — https://help.zoho.com/portal/en/kb/desk/developer-space/asap/react-native-sdk
0/10Repository description
0/10Topics
10/10Wiki
Inputs used
topics—
has_wikiyes
homepage—
docs_sitehttps://help.zoho.com/portal/en/kb/desk/developer-space/asap/react-native-sdk
has_readmeno
has_docs_dirno
has_descriptionno

Security

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

36Weak · 16% of overall
How it's scored
6/7.5Binary-Artifacts — binaries present in source code
0/7.5Branch-Protection — branch protection not enabled on development/release branches
2/2.5CI-Tests — 5 out of 6 merged PRs checked by a CI test -- score normalized to 8
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
7.5/7.5Code-Review — all changesets reviewed
0/2.5Contributors — project has 0 contributing companies or organizations -- score normalized to 0
0/10Dangerous-Workflow — no data
0/7.5Dependency-Update-Tool — no update tool detected
0/5Fuzzing — project is not fuzzed
0/2.5License — license file not detected
2.2/7.5Maintained — 4 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 3
0/5Packaging — no data
0/5Pinned-Dependencies — no data
0/5SAST — SAST tool is not run on all commits -- score normalized to 0
0/5Security-Policy — security policy file not detected
0/7.5Signed-Releases — no data
0/7.5Token-Permissions — no data
7.5/7.5Vulnerabilities — 0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated13
scorecard_versionv5.5.0
checks_inconclusive5
scorecard_aggregate3.6
Excluded from scoring (no data or not applicable): Dangerous-Workflow, Packaging, Pinned-Dependencies, Signed-Releases, Token-Permissions. 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.

34At Risk · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
11.2/40Legible commit history — 21 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.21
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
12.6/18One-command bootstrap — zohodesk-portal-apikit/android/build.gradle, zohodesk-portal-chatkit/android/build.gradle, zohodesk-portal-community/android/build.gradle (toolchain convention, no task runner)
0/22Automated tests
0/11Lint / format config
11/11Static type checking — Kotlin (statically typed)
0/10Reproducible environment
0/10Demonstrated agent practice — no agent-authored commits among the last 100
0/8Automated maintenance — no automated dependency updates observed
0/10OpenSSF Scorecard: Pinned-Dependencies — no data
Inputs used
has_nixno
has_testsno
lockfiles—
has_dockerfileno
typed_languageyes
bootstrap_files—
has_devcontainerno
has_linter_configno
typecheck_configs—
agent_commit_share0
toolchain_manifestszohodesk-portal-apikit/android/build.gradle, zohodesk-portal-chatkit/android/build.gradle, zohodesk-portal-community/android/build.gradle, zohodesk-portal-configuration/android/build.gradle, zohodesk-portal-core/android/build.gradle, zohodesk-portal-kb/android/build.gradle, zohodesk-portal-salesiq/android/build.gradle, zohodesk-portal-ticket/android/build.gradle
dependency_bot_commit_share0
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: Pinned-Dependencies. Remaining weights renormalized.
How it's scored
45/45Type-checkable code — Kotlin (statically typed)
55/55Manageable file sizes — 0/81 source files over 60KB
Inputs used
primary_languageKotlin
largest_source_bytes18,767
source_files_sampled81
oversized_source_files0

Key facts

10GitHub stars
8contributors
57commits, last 12 months
35days since last push
1releases
2bus factor
10open issues
npmpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token

More detail

Star and fork history 0 ★ / 7 ⇿
0Stars
7Forks
1Releases

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.

1234567712021-072024-022026-08
Major 0Minor 0Patch 1

Each point covers 5 days.

OpenSSF Scorecard 3.6 / 10
3.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-10-01 16:16 UTC

8Binary-Artifactsbinaries present in source code
0Branch-Protectionbranch protection not enabled on development/release branches
8CI-Tests5 out of 6 merged PRs checked by a CI test -- score normalized to 8
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
10Code-Reviewall changesets reviewed
0Contributorsproject has 0 contributing companies or organizations -- score normalized to 0
n/aDangerous-Workflowno workflows found
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
0Licenselicense file not detected
3Maintained4 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 3
n/aPackagingpackaging workflow not detected
n/aPinned-Dependenciesno dependencies found
0SASTSAST tool is not run on all commits -- score normalized to 0
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
n/aToken-PermissionsNo tokens found
10Vulnerabilities0 existing vulnerabilities detected
All dependencies 0

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

RegistryPackageVersionRelation
Dependency advisories not assessed

Advisory matching could not run for this report: No resolved dependencies to assess

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.34.0 — full methodology · metrics wiki.

How one result sits in the wider record: aggregate statistics — npm.