Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-11-18 12:49 UTC

editor-js / paragraph

Paragraph Tool for Editor.js 2.0

TypeScriptMIT★ 59 stars⑂ 128 forkssince Sep 2017View on GitHub ↗

editor-js/paragraph holds a health index of 23 out of 100, placing it in the At Risk band. It scores highest on Sustainability & Governance (68/100) and lowest on Vitality (1/100). It was last updated 701 days ago. 2 contributors account for most of its recent work.

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

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

Ownership

Editor.jsOrganization
572 followers37 public repossince Apr 2017

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
npm@editorjs/paragraph2.11.7753,22017701 days agocodex-editorparagrapheditor.jseditorjs

Metrics by category

Vitality

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

1Critical · 21% of overall
How it's scored
0/36Push recency — last push 701 days ago
0/36Commit cadence — 0/52 weeks with commits
0/18Commit volume — 0 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_year0
human_commit_share0.9
days_since_last_push701
active_weeks_last_year0
How it's scored
0/27Ships releases — no releases published
0/36Release recency — no releases
0/27Release cadence — no releases
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count0
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?

61Moderate · 17% of overall
How it's scored
28.6/60Stars — 59 stars
17.5/25Forks — 128 forks
1.7/15Watchers — 3 watchers
Inputs used
forks128
stars59
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_badges1
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_servicesbadgen.net
has_pull_request_templateno
How it's scored
78.4/80Monthly downloads — 753,220 downloads/month across npm
0/20Registry dependents — not reported by this ecosystem
Inputs used
packages@editorjs/paragraph
dependents—
ecosystemsnpm
total_downloads—
monthly_downloads753,220
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?

68Good · 23% of overall
How it's scored
25.2/54Bus factor — 2 contributor(s) cover half of all commits
15.3/22.5Commit distribution — top contributor authored 32% of commits
13.5/13.5Contributor breadth — 11 contributors
10/10OpenSSF Scorecard: Contributors — project has 8 contributing companies or organizations
Inputs used
bus_factor2
contributors_sampled11
top_contributor_share0.319
How it's scored
17.4/42Issue resolution — 41% of issues closed
23.3/30PR acceptance — 42/54 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
10.5/15OpenSSF Scorecard: Code-Review — Found 7/9 approved changesets -- score normalized to 7
Inputs used
merged_prs42
open_issues17
closed_issues12
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio0.414
closed_unmerged_prs12
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
19.8/25Owner reach — 572 followers of editor-js
23.5/25Track record — 37 public repos, account ~9 yr old
Inputs used
followers572
owner_typeOrganization
is_verifiedno
owner_logineditor-js
public_repos37
account_age_days3,496
How it's scored
25/25Published & resolvable — 1 package(s) on npm
14/35Publish recency — latest publish 701 days ago
20/20Version history — 17 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packages@editorjs/paragraph
ecosystemsnpm
any_deprecatedno
min_days_since_publish701

Engineering Quality

Are baseline engineering and documentation practices in place?

42Weak · 19% of overall
How it's scored
24/24CI workflows — 1 workflow(s)
0/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
6.4/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Tests — 0 out of 8 merged PRs checked by a CI test -- score normalized to 0
Inputs used
has_ciyes
has_testsno
has_editorconfigyes
has_linter_configno
has_precommit_configno

Documentation

60Moderate
How it's scored
30/30README
0/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
10/10Topics — 6 topics
10/10Wiki
Inputs used
topicseditor, codex, codex-editor, paragraph, text, plugin
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?

45Weak · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
0/7.5Branch-Protection — no data
0/2.5CI-Tests — 0 out of 8 merged PRs checked by a CI test -- score normalized to 0
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
5.2/7.5Code-Review — Found 7/9 approved changesets -- score normalized to 7
2.5/2.5Contributors — project has 8 contributing companies or organizations
10/10Dangerous-Workflow — no dangerous workflow patterns detected
7.5/7.5Dependency-Update-Tool — 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 — dependency not pinned by hash detected -- score normalized to 0
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 — detected GitHub workflow tokens with excessive permissions
0/7.5Vulnerabilities — 56 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated15
scorecard_versionv5.5.0
checks_inconclusive3
scorecard_aggregate4.1
high_risk_jurisdiction_cap34
high_risk_jurisdiction_multiplier75
security_posture_after_multiplier31
security_posture_before_jurisdiction41
Excluded from scoring (no data or not applicable): Branch-Protection, Packaging, Signed-Releases. Remaining weights renormalized. High-Risk Jurisdiction Policy applies a 75% multiplier and gives Security posture an At risk ceiling of 34.

Dependency advisories

100Exceptional
How it's scored
35/35Direct dependencies free of known advisories — no direct dependency carries a known advisory
25/25Indirect dependencies free of known advisories — no indirect dependency carries a known advisory
0/40No advisories left outstanding — no advisory carries a publication date
Inputs used
sourceosv
advisories0
affected_packages0
assessed_packages1
unassessed_packages0
affected_by_severitynone
direct_affected_packages0
Excluded from scoring (no data or not applicable): No advisories left outstanding. Remaining weights renormalized. Matched the npm:@editorjs/paragraph@2.11.7 runtime dependency closure — what installing the published package pulls in — 1 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.

42Weak · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
30.2/40Legible commit history — 51 of 90 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.567
agent_instruction_files—
agent_instruction_max_bytes—
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 100
8/8Automated maintenance — 10 of the last 100 commits are automated dependency updates
0/10OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsno
lockfilesyarn.lock
has_dockerfileno
typed_languageyes
bootstrap_files—
has_devcontainerno
has_linter_configno
typecheck_configstsconfig.json
agent_commit_share0
toolchain_manifests—
dependency_bot_commit_share0.1
How it's scored
45/45Type-checkable code — TypeScript (statically typed)
55/55Manageable file sizes — 0/4 source files over 60KB
Inputs used
primary_languageTypeScript
largest_source_bytes8,277
source_files_sampled4
oversized_source_files0

Key facts

59GitHub stars
11contributors
0commits, last 12 months
701days since last push
0releases
2bus factor
17open 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 ★ / 128 ⇿
0Stars
128Forks

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.

025507510012515012842018-112022-092026-07

Each point covers 7 days.

OpenSSF Scorecard 4.1 / 10
4.1aggregate

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-18 12:48 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 8 merged PRs checked by a CI test -- score normalized to 0
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
7Code-ReviewFound 7/9 approved changesets -- score normalized to 7
10Contributorsproject has 8 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate 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
0Vulnerabilities56 existing vulnerabilities detected
Direct dependencies 1
RegistryPackageVersion constraintManifest
npm@codexteam/icons^0.0.4package.json
All dependencies 111

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

RegistryPackageVersionRelation
npm@codexteam/icons0.0.4direct
npm@babel/parser7.24.6indirect
npm@editorjs/editorjs2.29.1indirect
npm@esbuild/android-arm0.18.20indirect
npm@esbuild/android-arm640.18.20indirect
npm@esbuild/android-x640.18.20indirect
npm@esbuild/darwin-arm640.18.20indirect
npm@esbuild/darwin-x640.18.20indirect
npm@esbuild/freebsd-arm640.18.20indirect
npm@esbuild/freebsd-x640.18.20indirect
npm@esbuild/linux-arm0.18.20indirect
npm@esbuild/linux-arm640.18.20indirect
npm@esbuild/linux-ia320.18.20indirect
npm@esbuild/linux-loong640.18.20indirect
npm@esbuild/linux-mips64el0.18.20indirect
npm@esbuild/linux-ppc640.18.20indirect
npm@esbuild/linux-riscv640.18.20indirect
npm@esbuild/linux-s390x0.18.20indirect
npm@esbuild/linux-x640.18.20indirect
npm@esbuild/netbsd-x640.18.20indirect
npm@esbuild/openbsd-x640.18.20indirect
npm@esbuild/sunos-x640.18.20indirect
npm@esbuild/win32-arm640.18.20indirect
npm@esbuild/win32-ia320.18.20indirect
npm@esbuild/win32-x640.18.20indirect
npm@jridgewell/sourcemap-codec1.4.15indirect
npm@microsoft/api-extractor7.43.0indirect
npm@microsoft/api-extractor-model7.28.13indirect
npm@microsoft/tsdoc0.14.2indirect
npm@microsoft/tsdoc-config0.16.2indirect
npm@rollup/pluginutils5.1.0indirect
npm@rushstack/node-core-library4.0.2indirect
npm@rushstack/rig-package0.5.2indirect
npm@rushstack/terminal0.10.0indirect
npm@rushstack/ts-command-line4.19.1indirect
npm@types/argparse1.0.38indirect
npm@types/estree1.0.5indirect
npm@volar/language-core1.11.1indirect
npm@volar/source-map1.11.1indirect
npm@volar/typescript1.11.1indirect
npm@vue/compiler-core3.4.27indirect
npm@vue/compiler-dom3.4.27indirect
npm@vue/language-core1.8.27indirect
npm@vue/shared3.4.27indirect
npmajv6.12.6indirect
npmargparse1.0.10indirect
npmbalanced-match1.0.2indirect
npmbrace-expansion1.1.11indirect
npmbrace-expansion2.0.1indirect
npmcommander9.5.0indirect
npmcomputeds0.0.1indirect
npmconcat-map0.0.1indirect
npmde-indent1.0.2indirect
npmdebug4.3.5indirect
npmentities4.5.0indirect
npmesbuild0.18.20indirect
npmestree-walker2.0.2indirect
npmfast-deep-equal3.1.3indirect
npmfast-json-stable-stringify2.1.0indirect
npmfs-extra7.0.1indirect
npmfsevents2.3.3indirect
npmfunction-bind1.1.2indirect
npmgraceful-fs4.2.11indirect
npmhas-flag4.0.0indirect
npmhasown2.0.2indirect
npmhe1.2.0indirect
npmimport-lazy4.0.0indirect
npmis-core-module2.13.1indirect
npmjju1.4.0indirect
npmjson-schema-traverse0.4.1indirect
npmjsonfile4.0.0indirect
npmkolorist1.8.0indirect
npmlodash4.17.21indirect
npmlodash.get4.4.2indirect
npmlodash.isequal4.5.0indirect
npmlru-cache6.0.0indirect
npmmagic-string0.30.10indirect
npmminimatch3.0.8indirect
npmminimatch9.0.4indirect
npmms2.1.2indirect
npmmuggle-string0.3.1indirect
npmnanoid3.3.6indirect
npmpath-browserify1.0.1indirect
npmpath-parse1.0.7indirect
npmpicocolors1.0.0indirect
npmpicomatch2.3.1indirect
npmpostcss8.4.31indirect
npmpunycode2.3.1indirect
npmresolve1.19.0indirect
npmresolve1.22.8indirect
npmrollup3.29.4indirect
npmsemver7.5.4indirect
npmsource-map0.6.1indirect
npmsource-map-js1.2.0indirect
npmsprintf-js1.0.3indirect
npmstring-argv0.3.2indirect
npmstrip-json-comments3.1.1indirect
npmsupports-color8.1.1indirect
npmsupports-preserve-symlinks-flag1.0.0indirect
npmtypescript5.4.2indirect
npmtypescript5.4.5indirect
npmuniversalify0.1.2indirect
npmuri-js4.4.1indirect
npmvalidator13.12.0indirect
npmvite4.4.11indirect
npmvite-plugin-css-injected-by-js3.3.0indirect
npmvite-plugin-dts3.9.1indirect
npmvue-template-compiler2.7.16indirect
npmvue-tsc1.8.27indirect
npmyallist4.0.0indirect
npmz-schema5.0.5indirect
Dependency advisories 0

Installing npm:@editorjs/paragraph@2.11.7 pulls in 1 packages, direct and transitive: 0 carry known advisories, of which 0 are direct dependencies.

No known advisories affect the assessed dependencies.

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.