@agentproto/providers-store

中文文档
0.4.4发布于 2026/11/06Apache-2.0TypeScriptES Module构建来源已验证近 30 天下载 5964

@agentproto/providers-store — the ~/.agentproto/providers.json LLM provider API-key store (mode 0600) and the injectProviderKeysIntoEnv helper that lets any process (daemon or standalone gateway) boot with keys set via agentproto auth provider set,

原始使用文档
文档目录3 节
  1. Usage
  2. API
  3. License

@agentproto/providers-store

The ~/.agentproto/providers.json LLM provider API-key store (mode 0600), written by agentproto auth provider set, and the injectProviderKeysIntoEnv helper that lets a process boot with those keys in its environment.

Before this store existed, the only way to give a process a provider key was an ambient export FOO_API_KEY=… in whatever shell launched it — invisible, easy to forget, per-shell. Set once via the CLI, every process that calls injectProviderKeysIntoEnv at boot picks it up.

This package is a leaf: node builtins + @agentproto/model-catalog only, so any standalone process (not just the @agentproto/runtime daemon) can depend on it without dragging in a full gateway.

Usage

import { injectProviderKeysIntoEnv } from "@agentproto/providers-store"

// Call once at process boot, before anything reads provider env vars.
// Explicit env always wins — a var already set is never overwritten.
const injected = await injectProviderKeysIntoEnv(process.env)
if (injected.length > 0) {
  console.error(`loaded ${injected.length} provider key(s) from store: ${injected.join(", ")}`)
}

Keys never leave the store except into the caller's own process env; they are never logged — only provider names, never values, should reach output.

API

  • loadProviders() / setProviderKey(provider, apiKey, baseUrl?) / removeProviderKey(provider) / getProviderKey(provider) — read/write providers.json.
  • injectProviderKeysIntoEnv(env?) — injects stored keys into env (default process.env), skipping any name already set. Returns the list of provider names actually injected.
  • providerEnvVar(provider) / PROVIDER_ENV_VARS — canonical provider → env-var-name mapping (derived from @agentproto/model-catalog's PROVIDER_KEY_ENV, plus the non-catalog gateway providers this store also fronts).
  • providersPath() — resolves ~/.agentproto/providers.json.

@agentproto/runtime re-exports this package's surface unchanged (including the @agentproto/runtime/providers-store subpath) for existing consumers.

License

Apache-2.0

版本与发布记录

@agentproto/providers-store 共发布 36 个版本,首次发布于 2026/07/16;过去 12 个月发布了 36 个版本。最新版本附带 npm provenance 构建来源证明,可追溯到公开的 CI 构建记录。

版本发布日期距今
0.4.4latest2026/11/06今天
0.4.32026/11/042 天前
0.4.22026/11/014 天前
0.4.12026/10/279 天前
0.4.02026/10/2314 天前
0.3.322026/10/1917 天前

关于 @agentproto/providers-store 的常见问题

@agentproto/providers-store 是什么?

@agentproto/providers-store — the ~/.agentproto/providers.json LLM provider API-key store (mode 0600) and the injectProviderKeysIntoEnv helper that lets any process (daemon or standalone gateway) boot with keys set via agentproto auth provider set,

如何安装 @agentproto/providers-store?

在项目目录运行 npm install @agentproto/providers-store,或使用 pnpm add / yarn add / bun add。

@agentproto/providers-store 支持 TypeScript 吗?

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

@agentproto/providers-store 支持 ESM 还是 CommonJS?

以 ES Module 形式发布,推荐使用 import 引入。在 CommonJS 项目中,Node.js 20.19+ / 22.12+ 可以直接 require() 不含顶层 await 的 ES Module,更早的版本需要改用动态 import()。

@agentproto/providers-store 需要什么版本的 Node.js?

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

@agentproto/providers-store 可以商用吗?

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

@agentproto/providers-store 的下载量有多少?

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

@agentproto/providers-store 还在维护吗?

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