registry / privateer-agent / 0.3.0

privateer-agent@0.3.0

Privateer — a provider-agnostic, safe-by-default terminal coding agent with TEE/Tinfoil attestation, rebuilt on the Pi toolkit. Bring your own model across 20 providers.

AI Security Review

scanned 2d ago · by lpm-firewall-ai

Manual review required because source files were not inspected.

Static reason

No blocking static signals were detected.

Trigger

unknown

Impact

unknown

Mechanism

unknown

Rationale

Unable to access read-only filesystem inspection tools in the required final JSON response context.

Decision evidence

public snapshot

AI called this Manual Review at 0.0% confidence as Unknown with high false-positive risk.

Evidence for warning

Inspection could not be performed in this environment because only final JSON output is available.

Evidence against

Behavioral surface

Source

CryptoDynamicRequireEnvironmentVarsFilesystemNetworkWebSocket

Supply chain

HighEntropyStringsUrlStrings

ManifestNo manifest risk signals triggered.

scanned 38 file(s), 194 KB of source, external domains: dashscope-intl.aliyuncs.com, helix-server-m1ac.onrender.com, openrouter.ai

Source & flagged code

1 flagged

bin/privateer.mjsView file

Lines 1-23javascript

1#!/usr/bin/env node

2// Launcher for the privateer 0.3 agent REPL. It runs in the DIRECTORY YOU INVOKE

3// IT FROM (process.cwd() — that's the agent's working dir), while resolving the

4// code and dev keys from the repo. Prefer the `bin/pv` wrapper, which also picks a

5// Node >= 22 (the Pi stack's floor).

6import { register } from "tsx/esm/api";

7import { fileURLToPath } from "node:url";

8import { dirname, resolve } from "node:path";

10const here = dirname(fileURLToPath(import.meta.url));

11const repo = resolve(here, "..");

13// Dev convenience: load provider keys from the repo's .env if present, WITHOUT

14// changing cwd. (A real install would rely on env vars / ~/.privateer instead.)

15try {

16 process.loadEnvFile(resolve(repo, ".env"));

17} catch {

18 /* no .env — fall back to the ambient environment */

19}

21register(); // resolves the repo's tsx regardless of the invocation cwd

22await import(resolve(repo, "src/cli/chat.ts"));

Medium

Dynamic Require

Package source references dynamic require/import behavior.

bin/privateer.mjsView on unpkg · L21

Source & flagged code

1 flagged · loading source

bin/privateer.mjsView file

21register(); // resolves the repo's tsx regardless of the invocation cwd L22: await import(resolve(repo, "src/cli/chat.ts"));

Medium

Dynamic Require

Package source references dynamic require/import behavior.

bin/privateer.mjsView on unpkg · L21

Findings

3 Medium4 Low

MediumDynamic Requirebin/privateer.mjs

MediumNetwork

MediumEnvironment Vars

LowScripts Present

LowFilesystem

LowHigh Entropy Strings

LowUrl Strings

Source & flagged code

1 flagged

bin/privateer.mjsView file

Lines 1-23javascript

1#!/usr/bin/env node

2// Launcher for the privateer 0.3 agent REPL. It runs in the DIRECTORY YOU INVOKE

3// IT FROM (process.cwd() — that's the agent's working dir), while resolving the

4// code and dev keys from the repo. Prefer the `bin/pv` wrapper, which also picks a

5// Node >= 22 (the Pi stack's floor).

6import { register } from "tsx/esm/api";

7import { fileURLToPath } from "node:url";

8import { dirname, resolve } from "node:path";

10const here = dirname(fileURLToPath(import.meta.url));

11const repo = resolve(here, "..");

13// Dev convenience: load provider keys from the repo's .env if present, WITHOUT

14// changing cwd. (A real install would rely on env vars / ~/.privateer instead.)

15try {

16 process.loadEnvFile(resolve(repo, ".env"));

17} catch {

18 /* no .env — fall back to the ambient environment */

19}

21register(); // resolves the repo's tsx regardless of the invocation cwd

22await import(resolve(repo, "src/cli/chat.ts"));

Medium

Dynamic Require

Package source references dynamic require/import behavior.

bin/privateer.mjsView on unpkg · L21