Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-11-21 19:44 UTC

groupdocs-conversion-cloud / groupdocs-conversion-cloud-node

Node.js SDK to communicate with the GroupDocs.Conversion REST API. Convert between 50+ document & image formats with zero initial cost.

TypeScriptMIT★ 2 stars⑂ 1 forksince Oct 2018View on GitHub ↗

groupdocs-conversion-cloud/groupdocs-conversion-cloud-node holds a health index of 34 out of 100, placing it in the At Risk band. It scores highest on Engineering Quality (48/100) and lowest on Security (25/100). It was last updated 99 days ago. A single contributor accounts for most of its recent work.

34
overall / 100
At Risk

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.

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

Ownership

12 followers21 public repossince Jan 2018

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
npmgroupdocs-conversion-cloud26.8.07,8573899 days agogroupdocscloudconversion

Metrics by category

Vitality

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

43Weak · 21% of overall
How it's scored
9.9/36Push recency — last push 99 days ago
2.1/36Commit cadence — 3/52 weeks with commits
5.4/18Commit volume — 3 commits in the last year
0/10OpenSSF Scorecard: Maintained — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Inputs used
commits_last_year3
human_commit_share1
days_since_last_push99
active_weeks_last_year3
How it's scored
27/27Ships releases — 36 releases published
27/36Release recency — latest release 99 days ago
19.8/27Release cadence — a release every ~58 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count36
latest_release_tagv26.8
releases_from_tagsno
days_since_latest_release99
mean_days_between_releases58
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?

35Weak · 17% of overall
How it's scored
0/60Stars — 2 stars
0/25Forks — 1 forks
1.7/15Watchers — 3 watchers
Inputs used
forks1
stars2
watchers3
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5License — recognized 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_badges0
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_services—
has_pull_request_templateno
How it's scored
51.9/80Monthly downloads — 7,857 downloads/month across npm
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagesgroupdocs-conversion-cloud
dependents—
ecosystemsnpm
total_downloads—
monthly_downloads7,857
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?

41Weak · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
3.1/22.5Commit distribution — top contributor authored 86% of commits
8.1/13.5Contributor breadth — 6 contributors
0/10OpenSSF Scorecard: Contributors — project has 0 contributing companies or organizations -- score normalized to 0
Inputs used
bus_factor1
contributors_sampled6
top_contributor_share0.863
How it's scored
0/42Issue resolution — 0% of issues closed
0/30PR acceptance — 0/5 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-Review — Found 0/30 approved changesets -- score normalized to 0
Inputs used
merged_prs0
open_issues2
closed_issues0
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio0
closed_unmerged_prs5
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
0/20Verified domain
8/25Owner reach — 12 followers of groupdocs-conversion-cloud
21.8/25Track record — 21 public repos, account ~8 yr old
Inputs used
followers12
owner_typeOrganization
is_verifiedno
owner_logingroupdocs-conversion-cloud
public_repos21
account_age_days3,237

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 1 package(s) on npm
35/35Publish recency — latest publish 99 days ago
20/20Version history — 38 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesgroupdocs-conversion-cloud
ecosystemsnpm
any_deprecatedno
min_days_since_publish99

Engineering Quality

Are baseline engineering and documentation practices in place?

48Weak · 19% of overall
How it's scored
0/24CI workflows
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Tests — no data
Inputs used
has_cino
has_testsyes
has_editorconfigno
has_linter_configno
has_precommit_configno
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: CI-Tests. Remaining weights renormalized.
How it's scored
30/30README
0/25Documentation directory
15/15Documentation / homepage site — https://products.groupdocs.cloud/conversion/nodejs
10/10Repository description
10/10Topics — 12 topics
10/10Wiki
Inputs used
topicsconversion-cloud-api, nodejs, npm, convert-files, word, excel, powerpoint, visio, djvu, tiff, pdf, xps
has_wikiyes
homepagehttps://products.groupdocs.cloud/conversion/nodejs
docs_sitehttps://products.groupdocs.cloud/conversion/nodejs
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

25At Risk · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
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
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
2.5/2.5License — license file detected
0/7.5Maintained — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
0/5Packaging — no data
0/5Pinned-Dependencies — no data
0/5SAST — no SAST tool detected
0/5Security-Policy — security policy file not detected
0/7.5Signed-Releases — no data
0/7.5Token-Permissions — no data
0/7.5Vulnerabilities — 56 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated12
scorecard_versionv5.5.0
checks_inconclusive6
scorecard_aggregate1.5
Excluded from scoring (no data or not applicable): CI-Tests, Dangerous-Workflow, Packaging, Pinned-Dependencies, Signed-Releases, Token-Permissions. Remaining weights renormalized.
How it's scored
9.4/35Direct dependencies free of known advisories — 2 affected: axios 1.14.0 (high 8.7), qs 6.15.0 (moderate 5.3)
25/25Indirect dependencies free of known advisories — no indirect dependency carries a known advisory
29.6/40No advisories left outstanding — 2 advisory-carrying package(s) unaddressed past 90 days; oldest published 226 days ago
Inputs used
sourceosv
advisories38
affected_packages2
assessed_packages42
unassessed_packages0
affected_by_severityhigh 1, moderate 1
direct_affected_packages2
Matched the npm:groupdocs-conversion-cloud@26.8.0 runtime dependency closure — what installing the published package pulls in — 42 packages. Reachability is not analyzed.

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.

45Weak · 4% of overall
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://docs.groupdocs.cloud/llms.txt)
0/40Legible commit history — 0 of 51 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtyes
llms_txt_urlhttps://docs.groupdocs.cloud/llms.txt
legible_history_share0
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
0/18One-command bootstrap
22/22Automated tests
0/11Lint / format config
11/11Static type checking — tsconfig.json
10/10Reproducible environment — lockfile
0/10Demonstrated agent practice — no agent-authored commits among the last 51
0/8Automated maintenance — no automated dependency updates observed
0/10OpenSSF Scorecard: Pinned-Dependencies — no data
Inputs used
has_nixno
has_testsyes
lockfilespackage-lock.json
has_dockerfileno
typed_languageyes
bootstrap_files—
has_devcontainerno
has_linter_configno
typecheck_configstsconfig.json
agent_commit_share0
toolchain_manifests—
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 — TypeScript (statically typed)
51.3/55Manageable file sizes — 1/15 source files over 60KB
Inputs used
primary_languageTypeScript
largest_source_bytes143,715
source_files_sampled15
oversized_source_files1

Key facts

2GitHub stars
6contributors
3commits, last 12 months
99days since last push
36releases
1bus factor
2open issues
npmpackage ecosystems

Data collection warnings

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

More detail

OpenSSF Scorecard 1.5 / 10
1.5aggregate

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-11-21 19:44 UTC

10Binary-Artifactsno binaries found in the repo
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
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
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
n/aPinned-Dependenciesno dependencies found
0SASTno SAST tool detected
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
n/aToken-PermissionsNo tokens found
0Vulnerabilities56 existing vulnerabilities detected
Direct dependencies 4
RegistryPackageVersion constraintManifest
npmaxios1.14.0package.json
npmform-data*package.json
npmjsonwebtoken9.0.1package.json
npmqs6.15.0package.json
All dependencies 173

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

RegistryPackageVersionRelation
npmaxios1.14.0direct
npmform-data4.0.5direct
npmjsonwebtoken9.0.1direct
npmqs6.15.0direct
npm@babel/code-frame7.24.7indirect
npm@babel/helper-validator-identifier7.24.7indirect
npm@babel/highlight7.24.7indirect
npm@isaacs/cliui8.0.2indirect
npm@pkgjs/parseargs0.11.0indirect
npm@types/chai4.3.17indirect
npm@types/jsonwebtoken9.0.1indirect
npm@types/mocha5.2.7indirect
npm@types/node12.20.55indirect
npm@types/qs6.9.15indirect
npmansi-regex5.0.1indirect
npmansi-regex6.2.2indirect
npmansi-styles3.2.1indirect
npmansi-styles4.3.0indirect
npmansi-styles6.2.3indirect
npmarg4.1.3indirect
npmargparse1.0.10indirect
npmargparse2.0.1indirect
npmassertion-error1.1.0indirect
npmasynckit0.4.0indirect
npmbalanced-match1.0.2indirect
npmbrace-expansion1.1.13indirect
npmbrace-expansion2.0.3indirect
npmbrowser-stdout1.3.1indirect
npmbuffer-equal-constant-time1.0.1indirect
npmbuffer-from1.1.2indirect
npmbuiltin-modules1.1.1indirect
npmcall-bind-apply-helpers1.0.2indirect
npmcall-bound1.0.4indirect
npmcamelcase6.3.0indirect
npmchai4.5.0indirect
npmchalk2.4.2indirect
npmchalk4.1.2indirect
npmcheck-error1.0.3indirect
npmchokidar4.0.3indirect
npmcliui8.0.1indirect
npmcolor-convert1.9.3indirect
npmcolor-convert2.0.1indirect
npmcolor-name1.1.3indirect
npmcolor-name1.1.4indirect
npmcombined-stream1.0.8indirect
npmcommander2.20.3indirect
npmconcat-map0.0.1indirect
npmcross-spawn7.0.6indirect
npmdebug4.4.3indirect
npmdecamelize4.0.0indirect
npmdeep-eql4.1.4indirect
npmdelayed-stream1.0.0indirect
npmdiff4.0.4indirect
npmdiff7.0.0indirect
npmdunder-proto1.0.1indirect
npmeastasianwidth0.2.0indirect
npmecdsa-sig-formatter1.0.11indirect
npmemoji-regex8.0.0indirect
npmemoji-regex9.2.2indirect
npmes-define-property1.0.1indirect
npmes-errors1.3.0indirect
npmes-object-atoms1.1.1indirect
npmes-set-tostringtag2.1.0indirect
npmescalade3.2.0indirect
npmescape-string-regexp1.0.5indirect
npmescape-string-regexp4.0.0indirect
npmesprima4.0.1indirect
npmfind-up5.0.0indirect
npmflat5.0.2indirect
npmfollow-redirects1.15.11indirect
npmforeground-child3.3.1indirect
npmfs.realpath1.0.0indirect
npmfunction-bind1.1.2indirect
npmget-caller-file2.0.5indirect
npmget-func-name2.0.2indirect
npmget-intrinsic1.3.0indirect
npmget-proto1.0.1indirect
npmglob10.5.0indirect
npmglob7.2.3indirect
npmgopd1.2.0indirect
npmhas-flag3.0.0indirect
npmhas-flag4.0.0indirect
npmhas-symbols1.1.0indirect
npmhas-tostringtag1.0.2indirect
npmhasown2.0.2indirect
npmhe1.2.0indirect
npminflight1.0.6indirect
npminherits2.0.4indirect
npmis-core-module2.15.0indirect
npmis-fullwidth-code-point3.0.0indirect
npmis-path-inside3.0.3indirect
npmis-plain-obj2.1.0indirect
npmis-unicode-supported0.1.0indirect
npmisexe2.0.0indirect
npmjackspeak3.4.3indirect
npmjs-tokens4.0.0indirect
npmjs-yaml3.14.2indirect
npmjs-yaml4.1.1indirect
npmjwa1.4.2indirect
npmjws3.2.3indirect
npmlocate-path6.0.0indirect
npmlodash4.18.1indirect
npmlog-symbols4.1.0indirect
npmloupe2.3.7indirect
npmlru-cache10.4.3indirect
npmmake-error1.3.6indirect
npmmath-intrinsics1.1.0indirect
npmmime-db1.52.0indirect
npmmime-types2.1.35indirect
npmminimatch3.1.5indirect
npmminimatch9.0.9indirect
npmminimist1.2.8indirect
npmminipass7.1.3indirect
npmmkdirp0.5.6indirect
npmmocha11.7.5indirect
npmms2.1.3indirect
npmobject-inspect1.13.4indirect
npmonce1.4.0indirect
npmp-limit3.1.0indirect
npmp-locate5.0.0indirect
npmpackage-json-from-dist1.0.1indirect
npmpath-exists4.0.0indirect
npmpath-is-absolute1.0.1indirect
npmpath-key3.1.1indirect
npmpath-parse1.0.7indirect
npmpath-scurry1.11.1indirect
npmpathval1.1.1indirect
npmpicocolors1.1.1indirect
npmproxy-from-env2.1.0indirect
npmrandombytes2.1.0indirect
npmreaddirp4.1.2indirect
npmrequire-directory2.1.1indirect
npmresolve1.22.8indirect
npmsafe-buffer5.2.1indirect
npmsemver5.7.2indirect
npmsemver7.6.3indirect
npmserialize-javascript6.0.2indirect
npmshebang-command2.0.0indirect
npmshebang-regex3.0.0indirect
npmside-channel1.1.0indirect
npmside-channel-list1.0.0indirect
npmside-channel-map1.0.1indirect
npmside-channel-weakmap1.0.2indirect
npmsignal-exit4.1.0indirect
npmsource-map0.6.1indirect
npmsource-map-support0.5.21indirect
npmsprintf-js1.0.3indirect
npmstring-width4.2.3indirect
npmstring-width5.1.2indirect
npmstrip-ansi6.0.1indirect
npmstrip-ansi7.2.0indirect
npmstrip-json-comments3.1.1indirect
npmsupports-color5.5.0indirect
npmsupports-color7.2.0indirect
npmsupports-color8.1.1indirect
npmsupports-preserve-symlinks-flag1.0.0indirect
npmts-node8.10.2indirect
npmtslib1.14.1indirect
npmtslint5.20.1indirect
npmtsutils2.29.0indirect
npmtype-detect4.1.0indirect
npmtypescript5.5.4indirect
npmwhich2.0.2indirect
npmworkerpool9.3.4indirect
npmwrap-ansi7.0.0indirect
npmwrap-ansi8.1.0indirect
npmwrappy1.0.2indirect
npmy18n5.0.8indirect
npmyargs17.7.2indirect
npmyargs-parser21.1.1indirect
npmyargs-unparser2.0.0indirect
npmyn3.1.1indirect
npmyocto-queue0.1.0indirect
Dependency advisories 2

Installing npm:groupdocs-conversion-cloud@26.8.0 pulls in 42 packages, direct and transitive: 2 carry known advisories, of which 2 are direct dependencies.

PackageVersionRelationSeverityAdvisoriesFixed in
axios1.14.0directhigh341.20.0
qs6.15.0directmoderate46.16.1

An advisory means the version recorded in the dependency graph falls inside an advisory’s affected range. Reachability is not analysed, and the graph includes development and test pins — a finding may concern tooling rather than shipped software.

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.