docusign / docusign-esign-node-client
The Official Docusign Node.js Client Library used to interact with the eSign REST API. Send, sign, and approve documents using this client.
docusign/docusign-esign-node-client holds a health index of 65 out of 100, placing it in the Good band. It scores highest on Sustainability & Governance (77/100) and lowest on AI Readiness (36/100). It was last updated 3 days ago. 2 contributors account for most of its recent work.
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.
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 60 is calibrated to 65 on the published index scale (record calibration 2026-08-02).
Ownership
This repository is backed by an organization — shared, accountable stewardship that can outlive any single maintainer.
Package ecosystems
| Registry | Package | Version | Downloads / mo | Versions | Last publish | Tags |
|---|---|---|---|---|---|---|
| npm | docusign-esignpoints to another repo — not scored | 10.0.0 | 1,237,557 | 123 | 3 days ago | docusignsignatureesignatureesigndigitalelectronictransactiondocumentcertificatedtmpdf |
Metrics by category
Vitality
Is the project alive — is code being written and are releases shipping?
Development activity
How it's scored
| 36/36 | Push recency — last push 3 days ago |
| 5.5/36 | Commit cadence — 8/52 weeks with commits |
| 8.6/18 | Commit volume — 8 commits in the last year |
| 2/10 | OpenSSF Scorecard: Maintained — 3 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 2 |
Inputs used
| commits_last_year | 8 |
| human_commit_share | — |
| days_since_last_push | 3 |
| active_weeks_last_year | 8 |
Release discipline
How it's scored
| 27/27 | Ships releases — 87 releases published |
| 36/36 | Release recency — latest release 3 days ago |
| 19.8/27 | Release cadence — a release every ~49.3 days |
| 0/10 | OpenSSF Scorecard: Signed-Releases — no data |
Inputs used
| releases_count | 87 |
| latest_release_tag | v10.0.0 |
| releases_from_tags | no |
| days_since_latest_release | 3 |
| mean_days_between_releases | 49.3 |
Community & Adoption
Does the project have users, downloads, attention, and a welcoming setup for contributors?
Popularity & adoption
How it's scored
| 35.6/60 | Stars — 157 stars |
| 16.7/25 | Forks — 101 forks |
| 7.9/15 | Watchers — 27 watchers |
Inputs used
| forks | 101 |
| stars | 157 |
| watchers | 27 |
| growth_state | unverified |
| growth_factor_pct | 100 |
| growth_unverified_reason | no_history |
Community health
How it's scored
| 22.5/22.5 | README |
| 22.5/22.5 | License — recognized license (MIT) |
| 0/18 | CONTRIBUTING guide |
| 0/13.5 | Code of conduct |
| 0/7.2 | Issue template |
| 0/6.3 | PR template |
Inputs used
| has_readme | yes |
| has_license | yes |
| readme_badges | — |
| has_contributing | no |
| has_issue_template | no |
| has_code_of_conduct | no |
| readme_badge_services | — |
| has_pull_request_template | no |
Sustainability & Governance
Will the project survive its people — bus factor, responsiveness, who backs it, and package upkeep?
Maintainer resilience (bus factor)
How it's scored
| 25.2/54 | Bus factor — 2 contributor(s) cover half of all commits |
| 12.2/22.5 | Commit distribution — top contributor authored 46% of commits |
| 13.5/13.5 | Contributor breadth — 34 contributors |
| 10/10 | OpenSSF Scorecard: Contributors — project has 5 contributing companies or organizations |
Inputs used
| bus_factor | 2 |
| contributors_sampled | 34 |
| top_contributor_share | 0.458 |
Issue & PR responsiveness
How it's scored
| 34.8/42 | Issue resolution — 83% of issues closed |
| 20.8/30 | PR acceptance — 142/205 decided PRs merged |
| 0/13 | Newcomer PR acceptance — no first-time contributor's PR decided in 30d |
| 15/15 | OpenSSF Scorecard: Code-Review — all changesets reviewed |
Inputs used
| merged_prs | 142 |
| open_issues | 30 |
| closed_issues | 145 |
| prs_merged_7d | — |
| prs_decided_7d | — |
| prs_merged_30d | — |
| prs_decided_30d | — |
| issue_closed_ratio | 0.829 |
| closed_unmerged_prs | 63 |
| first_time_authors_30d | — |
| first_time_prs_merged_30d | — |
| first_time_prs_decided_30d | — |
Ownership & stewardship
How it's scored
| 30/30 | Ownership backing — organization-owned |
| 0/20 | Verified domain — verified-domain status not read for this organization |
| 17.5/25 | Owner reach — 269 followers of docusign |
| 25/25 | Track record — 184 public repos, account ~16 yr old |
Inputs used
| followers | 269 |
| owner_type | Organization |
| is_verified | — |
| owner_login | docusign |
| public_repos | 184 |
| account_age_days | 5,916 |
Engineering Quality
Are baseline engineering and documentation practices in place?
Engineering practices
How it's scored
| 0/24 | CI workflows |
| 24/24 | Tests present |
| 0/16 | Linter config |
| 0/9.6 | Pre-commit hooks |
| 0/6.4 | .editorconfig |
| 0/20 | OpenSSF Scorecard: CI-Tests — 0 out of 29 merged PRs checked by a CI test -- score normalized to 0 |
Inputs used
| has_ci | no |
| has_tests | yes |
| has_editorconfig | no |
| has_linter_config | no |
| has_precommit_config | no |
Documentation
How it's scored
| 30/30 | README |
| 0/25 | Documentation directory |
| 15/15 | Documentation / homepage site — http://docusign.github.io/docusign-esign-node-client |
| 10/10 | Repository description |
| 10/10 | Topics — 8 topics |
| 10/10 | Wiki |
Inputs used
| topics | docusign-api, sdk, oauth, node, npm, package, esignature, electronic-signatures |
| has_wiki | yes |
| homepage | http://docusign.github.io/docusign-esign-node-client |
| docs_site | http://docusign.github.io/docusign-esign-node-client |
| has_readme | yes |
| has_docs_dir | no |
| has_description | yes |
Security
Are visible security and supply-chain practices strong, without unresolved high-risk jurisdiction exposure?
Security posture
How it's scored
| 7.5/7.5 | Binary-Artifacts — no binaries found in the repo |
| 0/7.5 | Branch-Protection — no data |
| 0/2.5 | CI-Tests — 0 out of 29 merged PRs checked by a CI test -- score normalized to 0 |
| 0/2.5 | CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected |
| 7.5/7.5 | Code-Review — all changesets reviewed |
| 2.5/2.5 | Contributors — project has 5 contributing companies or organizations |
| 0/10 | Dangerous-Workflow — no data |
| 7.5/7.5 | Dependency-Update-Tool — update tool detected |
| 0/5 | Fuzzing — project is not fuzzed |
| 2.5/2.5 | License — license file detected |
| 1.5/7.5 | Maintained — 3 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 2 |
| 0/5 | Packaging — no data |
| 0/5 | Pinned-Dependencies — no data |
| 0/5 | SAST — SAST tool is not run on all commits -- score normalized to 0 |
| 0/5 | Security-Policy — security policy file not detected |
| 0/7.5 | Signed-Releases — no data |
| 0/7.5 | Token-Permissions — no data |
| 7.5/7.5 | Vulnerabilities — 0 existing vulnerabilities detected |
Inputs used
| source | openssf_scorecard |
| checks_evaluated | 12 |
| scorecard_version | v5.5.0 |
| checks_inconclusive | 6 |
| scorecard_aggregate | 5.8 |
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.
Agent context & guidance
How it's scored
| 0/45 | Agent instructions — no CLAUDE.md / AGENTS.md / editor rules |
| 0/15 | Machine-readable docs (llms.txt) |
| 0/40 | Legible commit history — no data |
Inputs used
| has_llms_txt | no |
| llms_txt_url | — |
| legible_history_share | — |
| agent_instruction_files | — |
| agent_instruction_max_bytes | — |
How it's scored
| 0/18 | One-command bootstrap |
| 22/22 | Automated tests |
| 0/11 | Lint / format config |
| 11/11 | Static type checking — jsconfig.json |
| 0/10 | Reproducible environment |
| 0/10 | Demonstrated agent practice — no data |
| 0/8 | Automated maintenance — no data |
| 0/10 | OpenSSF Scorecard: Pinned-Dependencies — no data |
Inputs used
| has_nix | no |
| has_tests | yes |
| lockfiles | — |
| has_dockerfile | no |
| typed_language | no |
| bootstrap_files | — |
| has_devcontainer | no |
| has_linter_config | no |
| typecheck_configs | jsconfig.json |
| agent_commit_share | — |
| toolchain_manifests | — |
| dependency_bot_commit_share | — |
Code legibility for models
How it's scored
| 27/45 | Type-checkable code — JavaScript with type-check config (jsconfig.json) |
| 54.4/55 | Manageable file sizes — 7/665 source files over 60KB |
Inputs used
| primary_language | JavaScript |
| largest_source_bytes | 472,197 |
| source_files_sampled | 665 |
| oversized_source_files | 7 |
Key facts
Data collection warnings
- npm package 'docusign-esign' points at a different repository (https://github.com/docusign/docusign-node-client); excluded from ecosystem scoring
More detail
OpenSSF Scorecard 5.8 / 10
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).
| 10 | Binary-Artifacts | no binaries found in the repo |
| n/a | Branch-Protection | internal 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 |
| 0 | CI-Tests | 0 out of 29 merged PRs checked by a CI test -- score normalized to 0 |
| 0 | CII-Best-Practices | no effort to earn an OpenSSF best practices badge detected |
| 10 | Code-Review | all changesets reviewed |
| 10 | Contributors | project has 5 contributing companies or organizations |
| n/a | Dangerous-Workflow | no workflows found |
| 10 | Dependency-Update-Tool | update tool detected |
| 0 | Fuzzing | project is not fuzzed |
| 10 | License | license file detected |
| 2 | Maintained | 3 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 2 |
| n/a | Packaging | packaging workflow not detected |
| n/a | Pinned-Dependencies | no dependencies found |
| 0 | SAST | SAST tool is not run on all commits -- score normalized to 0 |
| 0 | Security-Policy | security policy file not detected |
| n/a | Signed-Releases | no releases found |
| n/a | Token-Permissions | No tokens found |
| 10 | Vulnerabilities | 0 existing vulnerabilities detected |
Direct dependencies 6
| Registry | Package | Version constraint | Manifest |
|---|---|---|---|
| npm | axios | ^1.6.8 | package.json |
| npm | @devhigley/parse-proxy | ^1.0.3 | package.json |
| npm | csv-stringify | ^1.0.0 | package.json |
| npm | jsonwebtoken | ^9.0.0 | package.json |
| npm | passport-oauth2 | ^1.6.1 | package.json |
| npm | safe-buffer | ^5.1.2 | package.json |
All dependencies 13
Full resolved dependency set from the GitHub dependency graph: 6 direct and 7 indirect (transitive) packages. The transitive closure is complete when the repository commits a lockfile.
| Registry | Package | Version | Relation |
|---|---|---|---|
| npm | @devhigley/parse-proxy | ^1.0.3 | direct |
| npm | axios | ^1.6.8 | direct |
| npm | csv-stringify | ^1.0.0 | direct |
| npm | jsonwebtoken | ^9.0.0 | direct |
| npm | passport-oauth2 | ^1.6.1 | direct |
| npm | safe-buffer | ^5.1.2 | direct |
| npm | docdash | 0.4.0 | indirect |
| npm | expect.js | ~0.3.1 | indirect |
| npm | jsdoc | 3.6.10 | indirect |
| npm | mocha | ~5.0.4 | indirect |
| npm | mocha-junit-reporter | ^1.18.0 | indirect |
| npm | pdf-parse-fork | ^1.2.0 | indirect |
| npm | semistandard | ^12.0.1 | indirect |
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.
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.15.0 — full methodology · metrics wiki.
How one result sits in the wider record: aggregate statistics — npm.