Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-26 22:40 UTC

ONLYOFFICE / doceditor-types

Apache-2.0★ 0 stars⑂ 1 forksince May 2026View on GitHub ↗
KindLibraryhow this is determined

ONLYOFFICE/doceditor-types holds a health index of 45 out of 100, placing it in the Weak band. It scores highest on Vitality (60/100) and lowest on AI Readiness (24/100). It was last updated 32 days ago. A single contributor accounts for most of its recent work.

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

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

Ownership

ONLYOFFICEOrganization · verified domain
4,858 followers272 public repossince Feb 2012

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
npm@onlyoffice/doceditor-types9.4.2152,352432 days agoonlyofficedocument-editordocs-apitypescripttypesdoceditor

Metrics by category

Vitality

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

60Moderate · 21% of overall

Development activity

42Weak
How it's scored
18/36Push recency — last push 32 days ago
4.8/36Commit cadence — 7/52 weeks with commits
11.9/18Commit volume — 20 commits in the last year
7/10OpenSSF Scorecard: Maintained — 9 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 7
Inputs used
commits_last_year20
human_commit_share1
days_since_last_push32
active_weeks_last_year7

Release discipline

88Excellent
How it's scored
16.2/27Ships releases — 4 version tags (no GitHub releases)
36/36Release recency — latest release 32 days ago
27/27Release cadence — a release every ~33 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count4
latest_release_tagv9.4.2
releases_from_tagsyes
days_since_latest_release32
mean_days_between_releases33
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?

39Weak · 17% of overall

Popularity & adoption

1Critical
How it's scored
0/60Stars — 0 stars
0/25Forks — 1 forks
0/15Watchers — 0 watchers
Inputs used
forks1
stars0
watchers0
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history

Community health

50Moderate
How it's scored
22.5/22.5README
22.5/22.5License — recognized 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_badges0
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_services—
has_pull_request_templateno

Ecosystem adoption (downloads)

86Excellent
How it's scored
69.1/80Monthly downloads — 152,352 downloads/month across npm
0/20Registry dependents — not reported by this ecosystem
Inputs used
packages@onlyoffice/doceditor-types
dependents—
ecosystemsnpm
total_downloads—
monthly_downloads152,352
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

Maintainer resilience (bus factor)

21At Risk
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
4.5/22.5Commit distribution — top contributor authored 80% of commits
4.1/13.5Contributor breadth — 3 contributors
3/10OpenSSF Scorecard: Contributors — project has 1 contributing companies or organizations -- score normalized to 3
Inputs used
bus_factor1
contributors_sampled3
top_contributor_share0.8

Issue & PR responsiveness

1Critical
How it's scored
0/42Issue resolution — no issues or no data
0/30PR acceptance — 0/1 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-Review — Found 0/20 approved changesets -- score normalized to 0
Inputs used
merged_prs0
open_issues0
closed_issues0
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio—
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): Issue resolution, Newcomer PR acceptance. Remaining weights renormalized.

Ownership & stewardship

100Exceptional
How it's scored
30/30Ownership backing — organization-owned
20/20Verified domain
25/25Owner reach — 4,858 followers of ONLYOFFICE
25/25Track record — 272 public repos, account ~14 yr old
Inputs used
followers4,858
owner_typeOrganization
is_verifiedyes
owner_loginONLYOFFICE
public_repos272
account_age_days5,342

Package maintenance

92Excellent
How it's scored
25/25Published & resolvable — 1 package(s) on npm
35/35Publish recency — latest publish 32 days ago
12/20Version history — 4 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packages@onlyoffice/doceditor-types
ecosystemsnpm
any_deprecatedno
min_days_since_publish32

Engineering Quality

Are baseline engineering and documentation practices in place?

40Weak · 19% of overall

Engineering practices

30At Risk
How it's scored
24/24CI workflows — 1 workflow(s)
0/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Tests — no data
Inputs used
has_ciyes
has_testsno
has_editorconfigno
has_linter_configno
has_precommit_configno
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: CI-Tests. Remaining weights renormalized.

Documentation

55Moderate
How it's scored
30/30README
0/25Documentation directory
15/15Documentation / homepage site — https://api.onlyoffice.com/docs/docs-api/usage-api/config/
0/10Repository description
0/10Topics
10/10Wiki
Inputs used
topics—
has_wikiyes
homepage—
docs_sitehttps://api.onlyoffice.com/docs/docs-api/usage-api/config/
has_readmeyes
has_docs_dirno
has_descriptionno

Security

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

48Weak · 16% of overall

Security posture

48Weak
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/20 approved changesets -- score normalized to 0
0.8/2.5Contributors — project has 1 contributing companies or organizations -- score normalized to 3
10/10Dangerous-Workflow — no dangerous workflow patterns detected
0/7.5Dependency-Update-Tool — no update tool detected
0/5Fuzzing — project is not fuzzed
2.5/2.5License — license file detected
5.2/7.5Maintained — 9 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 7
5/5Packaging — packaging workflow detected
0/5Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
0/5SAST — no SAST tool detected
0/5Security-Policy — security policy file not detected
0/7.5Signed-Releases — no data
6.8/7.5Token-Permissions — detected GitHub workflow tokens with excessive permissions
7.5/7.5Vulnerabilities — 0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate4.8
Excluded from scoring (no data or not applicable): CI-Tests, 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.

24At Risk · 4% of overall

Agent context & guidance

40Weak
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
40/40Legible commit history — 16 of 20 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.8
agent_instruction_files—
agent_instruction_max_bytes—

Verify loop (build / test / typecheck)

21At Risk
How it's scored
0/18One-command bootstrap
0/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 20
0/8Automated maintenance — no automated dependency updates observed
0/10OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsno
lockfilespackage-lock.json
has_dockerfileno
typed_languageno
bootstrap_files—
has_devcontainerno
has_linter_configno
typecheck_configstsconfig.json
agent_commit_share0
toolchain_manifests—
dependency_bot_commit_share0

Code legibility for models

1Critical
How it's scored
0/45Type-checkable code — primary language unknown
0/55Manageable file sizes — 1/1 source files over 60KB
Inputs used
primary_language—
largest_source_bytes163,249
source_files_sampled1
oversized_source_files1
Excluded from scoring (no data or not applicable): Type-checkable code. Remaining weights renormalized.

Key facts

0GitHub stars
3contributors
20commits, last 12 months
32days since last push
4releases
1bus factor
0open issues
npmpackage ecosystems

Data collection warnings

  • Language breakdown unavailable
  • GitHub dependency-graph SBOM unavailable (404); the dependency graph may be disabled for this repository

More detail

OpenSSF Scorecard 4.8 / 10
4.8aggregate

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-09-26 22:39 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/20 approved changesets -- score normalized to 0
3Contributorsproject has 1 contributing companies or organizations -- score normalized to 3
10Dangerous-Workflowno dangerous workflow patterns detected
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
7Maintained9 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 7
10Packagingpackaging workflow detected
0Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
0SASTno SAST tool detected
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
9Token-Permissionsdetected GitHub workflow tokens with excessive permissions
10Vulnerabilities0 existing vulnerabilities detected
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.

Related records

Inspected repositories sharing catalogue tags or ecosystems with ONLYOFFICE/doceditor-types. Read them side by side →

99apify/crawleeCrawlee—A web scraping and browser automation library for Node.js to build reliable crawlers. In JavaScript and TypeScript. Extract data for AI, LLMs, RAG, or GPTs. Download HTML, PDF, JPG, PNG, and other files from websites. Works with Puppeteer, Playwright, Cheerio, JSDOM, and raw HTTP. Both headful and headless mode. With proxy rotation.Exceptional98slackapi/node-slack-sdkSlack Developer Kit for Node.jsExceptional100clerk/javascriptOfficial JavaScript repository for Clerk authenticationExceptional100go-gitea/giteaGit with a cup of tea! Painless self-hosted all-in-one software development service, including Git hosting, code review, team collaboration, package registry and CI/CDExceptional100openai/openai-nodeOfficial JavaScript / TypeScript library for the OpenAI APIExceptional100Azure/azure-sdk-for-jsThis repository is for active development of the Azure SDK for JavaScript (NodeJS & Browser). For consumers of the SDK we recommend visiting our public developer docs at https://docs.microsoft.com/javascript/azure/ or our versioned developer docs at https://azure.github.io/azure-sdk-for-js. Exceptional

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.