@equs-ai/equs-credentials-sdk

中文文档
1.3.1发布于 2026/11/11Apache-2.0TypeScriptCommonJS近 30 天下载 6335

Node.js bindings for EQUS Credentials SDK, built as a native addon with NAPI-RS.

原始使用文档
文档目录5 节
  1. Prerequisites
  2. Installation
  3. Building and testing locally
  4. Usage
  5. Publishing

EQUS Credentials SDK wrappers for Node.js

Node.js bindings for EQUS Credentials SDK, built as a native addon with NAPI-RS.

Prerequisites

Installation

The wrapper is published as @equs-ai/equs-credentials-sdk; the native binary for your platform comes from a companion @equs-ai/equs-credentials-sdk-<os>-<arch> package. Both are on npmjs:

npm i @equs-ai/equs-credentials-sdk

Building and testing locally

Build the native binding, then run the test suite:

npm run build:debug   # required for tests — enables the `in-memory` and `test-fixtures` features
npm test

npm run build produces the release binary without the in-memory and test-fixtures features, so the tests will fail against it. Test files live in test/; their signed tokens and certificates are built at runtime through the fixture* functions the test-fixtures feature exports.

Usage

The package can be imported with both ES module and CommonJS syntax.

Publishing

Each platform binary is published as its own npm package, then the @equs-ai/equs-credentials-sdk package that depends on them is published on top. Both steps run from publish-nodejs.yml on a nodejs/vX.Y.Z tag — see Publish a New Release.

The two scripts the pipeline calls, for a manual run:

REGISTRY_URL_NPM=<registry-url> NPM_TOKEN=<token> TARGET=<target> ALIAS=<alias> ENVIRONMENT=production scripts/build_and_publish_target.sh
REGISTRY_URL_NPM=<registry-url> NPM_TOKEN=<token> ENVIRONMENT=production scripts/build_and_publish_wrapper.sh

Both scripts pack the package and publish the resulting .tgz, which the release manifest hashes. Neither writes an .npmrc: NPM_TOKEN is unset before the build and passed to npm publish alone as npm_config_//<registry>/:_authToken. In CI, REGISTRY_URL_NPM is https://registry.npmjs.org/ and NPM_TOKEN comes from the EQUS_CREDENTIALS_SDK_NPM_TOKEN organization secret.

The target list is napi.triples.additional in package.json; defaults is off, so napi prepublish lists only those three platforms in optionalDependencies.

版本与发布记录

@equs-ai/equs-credentials-sdk 共发布 7 个版本,首次发布于 2026/09/30;过去 12 个月发布了 7 个版本。

版本发布日期距今
1.3.1latest2026/11/112 天前
1.3.02026/11/0112 天前
1.2.02026/10/2915 天前
1.1.12026/10/2717 天前
1.1.02026/10/2222 天前
1.0.22026/10/021 个月前

关于 @equs-ai/equs-credentials-sdk 的常见问题

@equs-ai/equs-credentials-sdk 是什么?

Node.js bindings for EQUS Credentials SDK, built as a native addon with NAPI-RS.

如何安装 @equs-ai/equs-credentials-sdk?

在项目目录运行 npm install @equs-ai/equs-credentials-sdk,或使用 pnpm add / yarn add / bun add。

@equs-ai/equs-credentials-sdk 支持 TypeScript 吗?

支持。包内自带 TypeScript 类型声明(package.json 声明了 types 入口),安装后即可获得类型提示,无需再安装 @types 包。

@equs-ai/equs-credentials-sdk 支持 ESM 还是 CommonJS?

以 CommonJS 形式发布,可以直接 require();在 ES Module 项目中也可以用 import 引入(Node.js 会把 module.exports 作为默认导出)。

@equs-ai/equs-credentials-sdk 需要什么版本的 Node.js?

package.json 的 engines 字段要求 Node.js >= 10。版本不符时 npm 默认只给出警告,开启 engine-strict 后会拒绝安装。

@equs-ai/equs-credentials-sdk 可以商用吗?

@equs-ai/equs-credentials-sdk 使用 Apache-2.0 许可。宽松许可:允许商业使用、修改和再分发,并附带明确的专利授权;分发时需保留许可与 NOTICE 文件,修改过的文件要注明改动。以上为概括,不构成法律意见,请以许可原文为准。

@equs-ai/equs-credentials-sdk 的下载量有多少?

根据 npm 官方下载统计,@equs-ai/equs-credentials-sdk 在 2026/10/14 – 2026/11/12 这 30 天内被下载 6,335 次,日均约 211 次。下载量会把 CI 构建、镜像同步和作为其他包依赖的安装一并计入,适合横向比较热度,不能直接等同于使用人数。

@equs-ai/equs-credentials-sdk 还在维护吗?

最新版本 1.3.1 发布于 2026/11/11(2 天前);至今共发布 7 个版本,其中过去 12 个月发布了 7 个;首次发布于 2026/09/30。发布频率只是参考信号:功能稳定的工具可能很少需要更新,建议结合源码仓库的 issue 和提交记录判断。