registry / basedagents / 0.6.1

basedagents@0.6.1

SDK for the BasedAgents identity and reputation registry — register AI agents, sign requests, search the registry, and submit verifications

Static Scan Results

scanned 3h ago · by rust-scanner

Static analysis flagged 13 finding(s) at 72.0% confidence. This version is warn-only unless an AI or security-team review confirms malicious behavior.

Static reason

One or more suspicious static signals were detected.

Decision evidence

public snapshot

Behavioral surface

Source

ChildProcessCryptoDynamicRequireEnvironmentVarsEvalFilesystemNetworkShell

Supply chain

HighEntropyStringsUrlStrings

ManifestNo manifest risk signals triggered.

scanned 14 file(s), 126 KB of source, external domains: 127.0.0.1, api.basedagents.ai, basedagents.ai, example.com, json-schema.org, your-agent.example.com

Source & flagged code

4 flagged

dist/cli/keyring.jsView file

Lines 1-37javascript

1/**

2 * `basedagents keyring <args>` — a thin alias that forwards to the BasedAgents

3 * Keyring CLI (the @basedagents/keyring package).

4 *

5 * Why this exists: the docs, marketing, and agent.json canonicalize

6 * `npx basedagents keyring init`, but the keyring ships as its own package whose

7 * bin is `npx @basedagents/keyring init`. BOTH must work — agents run stale

8 * commands out of cached docs for months, so neither form can 404.

9 *

10 * Static dependency rule (homepage spec §4.6): @basedagents/keyring is a real

11 * dependency of `basedagents`, so installing `basedagents` (including via `npx

12 * basedagents`, which fetches deps) always brings the keyring with it. This

13 * alias therefore resolves the LOCAL copy and NEVER dynamic-fetches — a network

14 * call at this point would break inside a network-restricted sandbox whose task

15 * phase has no egress. If the local copy is somehow missing, we fail with a

16 * reinstall hint rather than silently reaching for the registry.

17 */

18import { spawnSync } from 'node:child_process';

19import { existsSync } from 'node:fs';

High

Child Process

Package source references child process execution.

dist/cli/keyring.jsView on unpkg · L17

High

Runtime Package Install

Package source invokes a package manager install command at runtime.

dist/cli/keyring.jsView on unpkg · L5

20import { fileURLToPath } from 'node:url';

21import * as path from 'node:path';

22/**

23 * Resolve the installed keyring bin (based.mjs) by walking node_modules.

24 *

25 * We deliberately do NOT use `require.resolve('@basedagents/keyring')`: the

26 * keyring package's "exports" map declares only an `import` condition (no

27 * `require`) and doesn't export `./package.json`, so CJS specifier resolution is

28 * blocked even when the package is installed right next to us. A plain

29 * filesystem walk up the node_modules chain isn't exports-gated and is robust to

30 * both hoisted installs and the npx cache layout — and it never touches the

31 * network, which is the whole point (§4.6 offline guarantee).

32 */

33function resolveLocalKeyringBin() {

34 let dir = path.dirname(fileURLToPath(import.meta.url));

35 for (;;) {

36 const bin = path.join(dir, 'node_modules', '@basedagents', 'keyring', 'bin', 'based.mjs');

37 if (existsSync(bin))

dist/scanner/index.jsView file

Lines 1-37javascript

1/**

2 * basedagents npm package security scanner

3 *

4 * Downloads an npm package tarball, extracts it, scans all JS/TS files

5 * for dangerous patterns, and returns a structured trust report.

6 */

7import { execFileSync } from 'child_process';

8import * as

Source & flagged code

4 flagged · loading source

dist/cli/keyring.jsView file

Static Scan Results

Decision evidence

Source & flagged code

Source & flagged code

Findings

Source & flagged code