@docusign/cli 1.0.0-rc

package/dist/templates/ai-skills/.claude/skills/ds-agreement-manager-workflow/SKILL.md

@@ -0,0 +1,331 @@
+---
+name: ds-agreement-manager-workflow
+description: Full Docusign Agreement Manager workflow guide — scaffold, auth, manifest, validate, upload, ingest, and test. Use when starting a new Agreement Manager project or asking how to set up AI document extraction with Docusign Agreement Manager.
+---
+
+# Docusign Agreement Manager Workflow
+
+Complete step-by-step guide for setting up AI-powered document extraction with Docusign Agreement Manager.
+
+## Quick Reference
+
+```bash
+ds auth login -e demo                                   # 1. Authenticate
+ds agm get catalog                                      # 2. Fetch standard catalog
+# Edit agreement-manager/configs/agreement-manager-manifest.json        # 3. Define types/fields
+ds agm validate                                         # 4. Validate manifest
+ds agm upload -y                                        # 5. Upload to platform
+ds agm ingest --directory ./agreement-manager/files/test -y    # 6. Ingest documents
+ds agm test generate-test-template -y                  # 7. Generate test CSV
+ds agm test run -y                                     # 8. Run tests
+```
+
+---
+
+## Step 1: Authenticate
+
+```bash
+ds auth login -e <environment>
+```
+
+**Environments:** `demo`, `production`
+
+Verify: `ds auth test`
+
+---
+
+## Step 2: Fetch Standard Catalog
+
+Download standard agreement types and fields available in your account:
+
+```bash
+ds agm get catalog
+```
+
+Creates in `agreement-manager/files/`:
+
+- `standard-catalog.json` — standard agreement types and fields
+- `custom-catalog.json` — existing custom types in your account
+
+Use these to reference standard field names and avoid naming conflicts.
+
+---
+
+## Step 3: Define Your Manifest
+
+**Location:** `agreement-manager/configs/agreement-manager-manifest.json`
+
+### Custom Fields
+
+```json
+{
+  "key": "C_TerminationDate",
+  "displayName": "Termination Date",
+  "aiDefinition": "The date on which this agreement or contract is terminated or expires.",
+  "category": "TerminationCategory",
+  "fieldType": "DateTime",
+  "customExtractionEnabled": true,
+  "examples": {
+    "en": [
+      { "exampleText": "This agreement shall terminate on December 31, 2025", "confirmedValue": "2025-12-31" },
+      { "exampleText": "Termination effective as of January 15, 2026", "confirmedValue": "2026-01-15" }
+    ]
+  }
+}
+```
+
+**Field rules:**
+
+- `key` must start with `C_` (e.g., `C_TerminationDate`)
+- `displayName` is the human-readable display name (referenced in agreement types)
+- `aiDefinition` describes what the field represents — required when `customExtractionEnabled: true`
+- `fieldType`: `String`, `Number`, `DateTime`, or `Dropdown`
+- `examples` required when `customExtractionEnabled: true` (3+ recommended)
+
+**Field categories:** `FinancialCategory`, `GeneralCategory`, `HumanResourcesCategory`, `LegalAndComplianceCategory`, `LifecycleCategory`, `PaymentCategory`, `RenewalCategory`, `TerminationCategory`, `OtherCategory`
+
+### Dropdown Fields
+
+```json
+{
+  "key": "C_TerminationReason",
+  "displayName": "Termination Reason",
+  "aiDefinition": "The reason why this agreement is being terminated.",
+  "fieldType": "Dropdown",
+  "customExtractionEnabled": true,
+  "dropdownOptions": [{ "name": "Performance Issues" }, { "name": "Cost Reduction" }, { "name": "Mutual Agreement" }, { "name": "Other" }],
+  "examples": {
+    "en": [{ "exampleText": "Due to repeated quality failures", "confirmedValue": "Performance Issues" }]
+  }
+}
+```
+
+### Custom Agreement Types
+
+```json
+{
+  "key": "C_SupplierTermination",
+  "displayName": "Supplier Termination Letter",
+  "aiDefinition": "A letter formally terminating a supplier agreement or vendor contract.",
+  "category": "BusinessServices",
+  "customExtractionEnabled": true,
+  "fields": {
+    "additionalStandardFields": ["Effective Date", "Company Name"],
+    "customFields": ["Termination Date", "Termination Reason"]
+  },
+  "docs": ["supplier-term-001.pdf", "supplier-term-002.pdf"]
+}
+```
+
+**Agreement type rules:**
+
+- `key` must start with `C_`
+- `displayName` is the human-readable name
+- `aiDefinition` describes the document type — required when `customExtractionEnabled: true`
+- `category`: `BusinessServices`, `HumanResources`, `Miscellaneous`, `OtherDocuments`
+- `customFields` references fields by `displayName`, not `key`
+- `additionalStandardFields` uses the display name from the standard catalog
+- `docs` are filenames only (not paths) — files must be in `agreement-manager/files/train/`
+
+### Extending Standard Agreement Types
+
+```json
+{
+  "key": "ConsultingDocumentData",
+  "displayName": "Consulting Agreement",
+  "fields": {
+    "additionalStandardFields": ["Payment Terms"],
+    "customFields": ["Project Code", "Hourly Rate"]
+  }
+}
+```
+
+---
+
+## Step 4: Validate
+
+```bash
+ds agm validate
+```
+
+| Error             | Cause                                                                | Fix                                |
+| ----------------- | -------------------------------------------------------------------- | ---------------------------------- |
+| name format       | Missing `C_` prefix                                                  | Add `C_` to custom field/type keys |
+| duplicate         | Same `displayName` used twice                                        | Rename one                         |
+| unreferenced      | Field not used by any type                                           | Add to a type or remove it         |
+| unknown field     | Type references undefined field `displayName`                        | Check displayName spelling         |
+| standard conflict | `displayName` conflicts with standard                                | Choose a different displayName     |
+| AI constraint     | `customExtractionEnabled: true` but missing examples or aiDefinition | Add both                           |
+| dropdown mismatch | confirmedValue not in dropdownOptions                                | Use exact option name              |
+
+---
+
+## Step 5: Upload
+
+```bash
+# Preview changes first
+ds agm upload --dry-run
+
+# Deploy to account
+ds agm upload -y
+```
+
+Upload is idempotent — re-uploading the same manifest is safe.
+
+---
+
+## Step 6: Ingest Documents
+
+```bash
+# Single file
+ds agm ingest --files ./agreement-manager/files/test/agreement.pdf -y
+
+# Directory
+ds agm ingest --directory ./agreement-manager/files/test -y
+
+# Recursive (includes subdirectories)
+ds agm ingest --directory ./agreement-manager/files/test --recursive -y
+
+# Preview
+ds agm ingest --directory ./agreement-manager/files/test --dry-run
+```
+
+**Supported formats:** PDF, DOCX, DOC, HTML, XLSX, XLS, XLSB, PPTX, PPT, PPSX, RTF, JPG, PNG, TIF
+
+Tracked in `agreement-manager/files/tracking.json` to prevent duplicate ingestion.
+
+---
+
+## Step 7: Generate Test Template
+
+```bash
+# Basic template
+ds agm test generate-test-template -y
+
+# Pre-fill with AI extractions from ingested documents
+ds agm test generate-test-template -y --prefill-extractions
+```
+
+Output: `agreement-manager/tests/testing.csv`
+
+The CSV has one row per ingested document and one column per field. Fill in your expected values to define what "correct" extraction looks like.
+
+For AI-assisted filling, use the `/ds-testing` skill.
+
+---
+
+## Step 8: Run Extraction Tests
+
+```bash
+# Exact match
+ds agm test run -y
+
+# Partial match (more lenient — good for long text fields)
+ds agm test run -y --partial-match
+```
+
+**Output:**
+
+- `agreement-manager/output/{timestamp}-field-test-results.csv` — field-level accuracy
+- `agreement-manager/output/{timestamp}-agreement-type-test-results.csv` — type classification accuracy
+
+---
+
+## Example: Complete Manifest
+
+```json
+{
+  "version": "1.0.0",
+  "defaultLocale": "en",
+  "namespace": "com.acme.supplier-management@1.0.0",
+  "standardAgreementTypes": [],
+  "customAgreementTypes": [
+    {
+      "key": "C_SupplierTermination",
+      "displayName": "Supplier Termination Letter",
+      "aiDefinition": "A letter formally terminating a supplier agreement or vendor contract.",
+      "category": "BusinessServices",
+      "customExtractionEnabled": true,
+      "fields": {
+        "additionalStandardFields": ["Effective Date", "Company Name"],
+        "customFields": ["Termination Date", "Termination Reason", "Notice Period Days"]
+      },
+      "docs": ["supplier-term-001.pdf", "supplier-term-002.pdf"]
+    }
+  ],
+  "fields": [
+    {
+      "key": "C_TerminationDate",
+      "displayName": "Termination Date",
+      "aiDefinition": "The date on which this agreement or contract is terminated or expires.",
+      "category": "TerminationCategory",
+      "fieldType": "DateTime",
+      "customExtractionEnabled": true,
+      "examples": {
+        "en": [
+          { "exampleText": "This agreement shall terminate on December 31, 2025", "confirmedValue": "2025-12-31" },
+          { "exampleText": "Termination effective as of January 15, 2026", "confirmedValue": "2026-01-15" },
+          { "exampleText": "termination is effective immediately as of the date of this agreement", "confirmedValue": "2025-08-20" }
+        ]
+      }
+    },
+    {
+      "key": "C_TerminationReason",
+      "displayName": "Termination Reason",
+      "aiDefinition": "The reason why this agreement is being terminated.",
+      "category": "TerminationCategory",
+      "fieldType": "Dropdown",
+      "customExtractionEnabled": true,
+      "dropdownOptions": [
+        { "name": "Performance Issues" },
+        { "name": "Cost Reduction" },
+        { "name": "Contract Expiration" },
+        { "name": "Mutual Agreement" },
+        { "name": "Convenience" },
+        { "name": "Other" }
+      ],
+      "examples": {
+        "en": [
+          { "exampleText": "Due to consistent quality issues with delivered components", "confirmedValue": "Performance Issues" },
+          { "exampleText": "Pursuant to Section 4.2a, termination is effective immediately", "confirmedValue": "Convenience" }
+        ]
+      }
+    },
+    {
+      "key": "C_NoticePeriodDays",
+      "displayName": "Notice Period Days",
+      "aiDefinition": "The number of days of advance notice required before termination takes effect.",
+      "category": "TerminationCategory",
+      "fieldType": "Number",
+      "customExtractionEnabled": true,
+      "examples": {
+        "en": [
+          { "exampleText": "with 30 days written notice as required by the agreement", "confirmedValue": "30" },
+          { "exampleText": "effective immediately (0 days notice)", "confirmedValue": "0" }
+        ]
+      }
+    }
+  ],
+  "metadata": {
+    "createdAt": "2025-01-01T00:00:00Z",
+    "updatedAt": "2025-01-01T00:00:00Z",
+    "version": "1.0.0",
+    "author": "Your Name",
+    "description": "Supplier termination letter extraction",
+    "tags": [],
+    "lastManifestHash": ""
+  }
+}
+```
+
+---
+
+## Iterating on Results
+
+If tests show low accuracy:
+
+1. **Add more examples** — 5–10 per field improves accuracy significantly
+2. **Improve aiDefinition** — be specific about what the field represents
+3. **Add training docs** — more diverse training documents in `agreement-manager/files/train/`
+4. **Check confirmedValues** — ensure examples use the exact format Navigator expects (e.g., ISO dates for DateTime)
+5. Re-upload and re-ingest after manifest changes

package/dist/templates/ai-skills/.claude/skills/ds-testing/SKILL.md

@@ -0,0 +1,130 @@
+---
+name: ds-testing
+description: AI-assisted Agreement Manager testing workflow. Reads your test documents, pre-fills expected values in the test CSV, runs extraction tests, and explains results. Use when you want to test how well Agreement Manager extracts fields from your documents.
+---
+
+# Docusign Agreement Manager Testing — AI-Assisted
+
+This skill guides you through the Navigator testing workflow by reading your documents, pre-filling the test CSV with expected values, running extraction tests, and interpreting results.
+
+## What This Skill Does
+
+1. Checks your test documents are ingested
+2. Generates the test CSV template
+3. **Reads each document** and fills in expected field values
+4. Runs the test
+5. Explains the results and suggests improvements
+
+---
+
+## Execution Steps
+
+### Step 1: Verify auth
+
+```bash
+ds auth test
+```
+
+If auth fails, prompt user to run `ds auth login -e <demo|production>`.
+
+### Step 2: Verify test documents
+
+Check `agreement-manager/files/test/` for documents. If empty, ask the user to add files (supported: PDF, DOCX, DOC, HTML, XLSX, XLS, XLSB, PPTX, PPT, PPSX, RTF, JPG, PNG, TIF).
+
+Check `agreement-manager/files/tracking.json` to see which files are already ingested.
+
+If documents exist but are not ingested:
+
+```bash
+ds agm ingest --directory ./agreement-manager/files/test -y
+```
+
+### Step 3: Generate test template with pre-filled extractions
+
+```bash
+ds agm test generate-test-template -y --prefill-extractions
+```
+
+This creates `agreement-manager/tests/testing.csv` with:
+
+- One row per ingested document
+- Platform's AI extraction results pre-filled where available
+- Empty cells where the platform couldn't extract a value
+
+### Step 4: Read the CSV and each document
+
+Read `agreement-manager/tests/testing.csv` to understand the structure:
+
+- Which documents are in the test
+- Which fields need expected values
+
+For each document listed in the CSV, read the document file (use the Read tool on PDF/DOCX). Extract the correct values for each field column based on the document's actual content.
+
+### Step 5: Fill in expected values
+
+Update `agreement-manager/tests/testing.csv`:
+
+- For each row (document), fill in the expected values for each field column
+- Use the field's `fieldType` to format values correctly:
+  - `DateTime`: ISO format `YYYY-MM-DD`
+  - `Number`: numeric value only (e.g., `1500`, not `$1,500`)
+  - `String`: the exact extracted text
+  - `Dropdown`: must match one of the `dropdownOptions` exactly
+- Leave a cell empty if the field genuinely does not appear in that document
+
+**Important:** Read `agreement-manager/configs/agreement-manager-manifest.json` to understand each field's type and dropdown options before filling values.
+
+### Step 6: Run the test
+
+```bash
+ds agm test run -y
+```
+
+### Step 7: Interpret results
+
+Read the output files:
+
+- `agreement-manager/output/{timestamp}-field-test-results.csv` — field-level results
+- `agreement-manager/output/{timestamp}-agreement-type-test-results.csv` — type classification results
+
+For each FAIL:
+
+| Failure Type          | Likely Cause                        | Suggestion                                                         |
+| --------------------- | ----------------------------------- | ------------------------------------------------------------------ |
+| Wrong value extracted | Poor examples in manifest           | Add more specific examples with exact text patterns from your docs |
+| Empty extraction      | Field not enabled or no examples    | Set `customExtractionEnabled: true` and add examples               |
+| Wrong agreement type  | AI not trained on your doc style    | Add more `docs` to the agreement type, add better `aiDefinition`   |
+| Dropdown value off    | Extracted text doesn't match option | Add example with that exact option as `confirmedValue`             |
+
+### Step 8: Report results to user
+
+Summarize:
+
+- Total tests: X passed, Y failed
+- Fields with failures and suggested fixes
+- Whether to re-upload manifest (`ds agm upload -y`) after changes
+
+---
+
+## CSV Format Reference
+
+```csv
+filename,Agreement Type [Custom],Termination Date [Custom],Notice Period Days [Custom],Company Name [Standard]
+supplier-term.pdf,Supplier Termination Letter,2025-12-31,30,Acme Corp
+change-order.pdf,Change Order,,15,BuildCo Inc
+```
+
+Column headers follow the pattern `{Field Label} [{Custom|Standard}]`.
+
+Leave cells empty (not `N/A`) when a field is not present in a document.
+
+---
+
+## Tips
+
+- Run with `--partial-match` for long text fields where exact match is too strict:
+  ```bash
+  ds agm test run -y --partial-match
+  ```
+- Re-ingest after adding new test documents (don't use `--dry-run`)
+- Multiple test runs produce timestamped result files — old results are preserved

package/dist/templates/ai-skills/.cursor/rules/docusign.mdc

@@ -0,0 +1,9 @@
+---
+description: Docusign Agreement Manager — IAM Toolkit CLI workflow guide for AI-powered document extraction
+globs: ["**/*.json", "**/*.csv", "**/agreement-manager/**"]
+alwaysApply: true
+---
+
+@file:.claude/skills/ds-agm-autopilot/SKILL.md
+@file:.claude/skills/ds-agreement-manager-workflow/SKILL.md
+@file:.claude/skills/ds-testing/SKILL.md

package/dist/templates/ai-skills/.gemini/instructions.md

@@ -0,0 +1,9 @@
+# Docusign Agreement Manager — Gemini CLI Instructions
+
+Read the following skill files for the full workflow guide and testing instructions:
+
+- `.claude/skills/ds-agm-autopilot/SKILL.md`
+- `.claude/skills/ds-agreement-manager-workflow/SKILL.md`
+- `.claude/skills/ds-testing/SKILL.md`
+
+These files contain step-by-step guidance for the `ds agm` CLI commands, manifest authoring rules, AI-assisted testing workflows, and full autopilot operation of the Agreement Manager lifecycle.

package/dist/templates/ai-skills/.github/instructions/docusign.instructions.md

@@ -0,0 +1,94 @@
+---
+applyTo: '**'
+---
+
+# Docusign Agreement Manager — AI Coding Instructions
+
+This workspace uses the Docusign IAM Toolkit CLI (`ds` command) for AI-powered document extraction with Docusign Agreement Manager.
+
+## Available CLI Commands
+
+```bash
+ds auth login -e <demo|production>  # Authenticate
+ds auth test                                           # Verify auth
+ds agm get catalog                                     # Fetch standard types/fields
+ds agm validate                                        # Validate manifest
+ds agm upload [-y|--dry-run]                           # Deploy manifest
+ds agm ingest --directory <path> [-y|--dry-run]        # Ingest documents
+ds agm test generate-test-template [-y] [--prefill-extractions]  # Create test CSV
+ds agm test run [-y] [--partial-match]                 # Run extraction tests
+```
+
+## Workspace Structure
+
+```
+<workspace>/
+├── .env
+└── <project>/
+    └── agreement-manager/
+        ├── configs/agreement-manager-manifest.json    # Define types/fields here
+        ├── files/
+        │   ├── train/                                 # Training documents
+        │   ├── test/                                  # Test documents
+        │   ├── tracking.json                          # Ingestion tracker
+        │   ├── standard-catalog.json                  # After 'get catalog'
+        │   └── custom-catalog.json
+        ├── tests/testing.csv                          # Test expectations
+        └── output/                                    # Test results
+```
+
+## Autopilot Mode
+
+To drive the full Agreement Manager lifecycle interactively, invoke the `ds-agm-autopilot` skill. It guides you through auth, manifest creation, upload, ingest, metadata ingestion, testing, and config migration with visual stage feedback. Say "autopilot" for autonomous operation or answer prompts step-by-step.
+
+## Agreement Manager Workflow
+
+1. `ds auth login -e demo`
+2. `ds agm get catalog`
+3. Edit `agreement-manager/configs/agreement-manager-manifest.json`
+4. `ds agm validate`
+5. `ds agm upload -y`
+6. Add documents to `agreement-manager/files/test/`, then `ds agm ingest --directory ./agreement-manager/files/test -y`
+7. `ds agm test generate-test-template -y --prefill-extractions`
+8. Fill expected values in `agreement-manager/tests/testing.csv`
+9. `ds agm test run -y`
+
+## Manifest Rules
+
+**Custom field `key`** must start with `C_` (e.g., `C_TerminationDate`). Use `displayName` for human-readable name. Add `aiDefinition` when `customExtractionEnabled: true`.
+
+**Field types:** `String`, `Number`, `DateTime`, `Dropdown`
+
+**Field categories:** `FinancialCategory`, `GeneralCategory`, `HumanResourcesCategory`, `LegalAndComplianceCategory`, `LifecycleCategory`, `PaymentCategory`, `RenewalCategory`, `TerminationCategory`, `OtherCategory`
+
+**Agreement type categories:** `BusinessServices`, `HumanResources`, `Miscellaneous`, `OtherDocuments`
+
+When `customExtractionEnabled: true`:
+
+- `examples` array is required (3+ recommended)
+- `aiDefinition` is required — describe what the field or document type represents
+- `docs` in agreement types reference filenames only (not paths)
+- `customFields` in agreement types reference fields by `displayName`, not `key`
+
+## Testing Workflow (AI-Assisted)
+
+When helping a user run extraction tests:
+
+1. Check files exist in `agreement-manager/files/test/`
+2. Check `tracking.json` — ingest any un-ingested files first
+3. Run `ds agm test generate-test-template -y --prefill-extractions`
+4. Read each test document and the manifest to understand expected values
+5. Fill `agreement-manager/tests/testing.csv` — use ISO dates (`YYYY-MM-DD`), numeric-only for Number fields, exact dropdown option names
+6. Run `ds agm test run -y`
+7. Read timestamped result CSVs in `agreement-manager/output/` and explain failures
+
+## Common Errors
+
+| Error             | Fix                                                              |
+| ----------------- | ---------------------------------------------------------------- |
+| name format       | Add `C_` prefix to custom field/type keys                        |
+| duplicate         | Rename one of the duplicate displayNames                         |
+| unreferenced      | Add field to a type's customFields or remove it                  |
+| unknown field     | customFields displayName doesn't match any field                 |
+| AI constraint     | Add examples and aiDefinition when customExtractionEnabled: true |
+| dropdown mismatch | confirmedValue must exactly match a dropdownOptions name         |

package/package.json

@@ -0,0 +1,90 @@
+{
+  "name": "@docusign/cli",
+  "version": "1.0.0-rc",
+  "author": "Docusign",
+  "description": "The Docusign CLI simplifies the implementation of Docusign Agreement Manager. With this CLI, you can bulk configure Agreement Manager with custom fields and types, map fields to types, provide AI training sets for custom extractions, programmatically test extraction accuracy, and export/import your setup across accounts. This offering is currently in beta.",
+  "main": "dist/index.mjs",
+  "license": "MIT",
+  "bin": {
+    "docusign": "./dist/index.mjs",
+    "ds": "./dist/index.mjs"
+  },
+  "files": [
+    "dist/index.mjs",
+    "dist/templates/"
+  ],
+  "scripts": {
+    "ado:build": "npm run build",
+    "ado:lint": "npm run lint",
+    "ado:test": "npm run test:unit",
+    "ado:version:validate": "ts-node scripts/validateVersion.ts",
+    "cli": "node dist/index.mjs",
+    "cli:dev": "ts-node src/index.ts",
+    "build": "tsc -p tsconfig.build.json && node scripts/build.mjs",
+    "postbuild": "",
+    "clean": "node -e \"require('fs-extra').removeSync('dist')\" && node -e \"require('fs-extra').removeSync('.build-intermediate')\"",
+    "prebuild": "npm run clean",
+    "prepare": "husky",
+    "prelink": "npm run build",
+    "link": "npm link",
+    "unlink": "npm unlink -g @docusign/cli",
+    "lint": "eslint .",
+    "lint:fix": "eslint . --fix",
+    "format:check": "prettier --check \"**/*.{ts,tsx,js,jsx,json,md}\"",
+    "format": "prettier --write \"**/*.{ts,tsx,js,jsx,json,md}\"",
+    "test": "npm run test:unit",
+    "test:watch": "jest --watch",
+    "test:coverage": "jest --coverage",
+    "test:verbose": "jest --verbose",
+    "test:unit": "jest",
+    "test:e2e": "jest --config jest.config.e2e.js",
+    "test:e2e:verbose": "jest --config jest.config.e2e.js --verbose"
+  },
+  "dependencies": {
+    "@inquirer/prompts": "^7.3.2",
+    "axios": "^1.7.9",
+    "chalk": "^4.1.2",
+    "commander": "^14.0.2",
+    "csv-parse": "^6.1.0",
+    "fs-extra": "^11.3.2",
+    "lodash": "^4.17.21",
+    "luxon": "^3.7.2",
+    "mixpanel": "^0.20.0",
+    "open": "^10.2.0",
+    "ora": "^9.3.0",
+    "reflect-metadata": "^0.2.2",
+    "semver": "^7.7.4",
+    "tslib": "^2.8.1",
+    "tsyringe": "^4.10.0",
+    "zod": "^4.1.12"
+  },
+  "devDependencies": {
+    "@eslint/js": "^9.39.1",
+    "@types/docusign-esign": "^5.19.9",
+    "@types/fs-extra": "^11.0.4",
+    "@types/jest": "^30.0.0",
+    "@types/luxon": "^3.7.1",
+    "@types/node": "^22.10.0",
+    "@types/semver": "^7.7.1",
+    "@typescript-eslint/eslint-plugin": "^8.46.3",
+    "@typescript-eslint/parser": "^8.46.3",
+    "docusign-esign": "^8.5.0",
+    "esbuild": "^0.27.3",
+    "eslint": "^9.39.1",
+    "eslint-config-prettier": "^10.1.8",
+    "eslint-plugin-import": "^2.32.0",
+    "eslint-plugin-jest": "^29.0.1",
+    "globals": "^16.5.0",
+    "husky": "^9.1.7",
+    "jest": "^30.2.0",
+    "jest-junit": "^16.0.0",
+    "prettier": "^3.6.2",
+    "ts-jest": "^29.4.5",
+    "ts-node": "^10.9.2",
+    "typescript": "^5.9.3",
+    "typescript-eslint": "^8.46.3"
+  },
+  "engines": {
+    "node": ">=22.0.0"
+  }
+}