registry / jungle-agents / 0.1.0

jungle-agents@0.1.0

Run Jungle agents on your own machine: `jungle-agents connect` registers this device and runs the agents you assign to it from the Jungle web app.

Static Scan Results

scanned 2h ago · by rust-scanner

Static analysis flagged 12 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

ChildProcessCryptoEnvironmentVarsFilesystemNetworkShellWebSocket

Supply chain

HighEntropyStringsUrlStrings

ManifestNo manifest risk signals triggered.

scanned 15 file(s), 129 KB of source, external domains: api.jungleagents.com, gmail.googleapis.com, www.googleapis.com

Source & flagged code

3 flagged

dist/git.jsView file

Lines 1-26javascript

1// GitHub credential handling for the SDK's child git/gh processes.

2// - Write ~/.git-credentials (https://x-access-token:TOKEN@github.com)

3// - Ensure `credential.helper store` in the global gitconfig

4// - Track GH_TOKEN so it can be injected into the SDK `env` for child processes

5// - Optionally clone the configured repo into /workspace/repo

6import { promises as fs } from "node:fs";

7import { spawn } from "node:child_process";

8import os from "node:os";

High

Child Process

Package source references child process execution.

dist/git.jsView on unpkg · L6

9import path from "node:path";

10import { log } from "./log.js";

11const HOME = process.env.HOME ?? os.homedir();

12// Portability (self-hosted): the repo clones inside the workspace (not a hardcoded /workspace), and

13// the credential store is redirectable via JUNGLE_GIT_CREDENTIALS. On a user's own machine the

14// daemon points JUNGLE_GIT_CREDENTIALS + GIT_CONFIG_GLOBAL into the agent's private state dir so the

15// agent never clobbers the person's real ~/.gitconfig / ~/.git-credentials. In a container both are

16// unset and this stays exactly as before (~/.git-credentials, global gitconfig).

17const WORKSPACE = process.env.JUNGLE_WORKSPACE ?? "/workspace";

18const CREDENTIALS_FILE = process.env.JUNGLE_GIT_CREDENTIALS ?? path.join(HOME, ".git-credentials");

19const REPO_DIR = path.join(WORKSPACE, "repo");

20// Latest known token, injected into the SDK env option (see runner.ts).

21let currentToken = null;

22export function getGhToken() {

23 return currentToken;

24}

25function run(cmd, args, opts = {}) {

26 return new Promise((resolve) => {

dist/cli.jsView file

Lines 1-29javascript

1#!/usr/bin/env node

2// `jungle-agents` — the CLI you run on a machine to make it a Jungle "environment". Typical use:

3//

4// jungle-agents connect # authenticate this device (browser), then run the daemon

5//

6// After connecting once you never touch the terminal again: pick this device as an agent's

7// environment in the Jungle web app, and the daemon runs that agent here. `up` re-runs the daemon

8// on a machine that's already connected (e.g. at login / in a service unit).

9import os from "node:os";

10import

Source & flagged code

3 flagged · loading source

dist/git.jsView file

6import { promises as fs } from "node:fs"; L7: import { spawn } from "node:child_process"; L8: import os from "node:os";

High

Child Process

Package source references child process execution.

dist/git.jsView on unpkg · L6

dist/cli.jsView file

High

Same File Env Network Execution

A single source file combines environment access, network access, and code or shell execution; review context before blocking.

dist/cli.jsView on unpkg · L9

9import os from "node:os"; L10: import { spawnSync } from "node:child_process"; L11: import { Daemon } from "./daemon.js"; L12: import { loadConfig, saveConfig, clearConfig, RUNNER_VERSION, } from "./config.js"; L13: const DEFAULT_BACKEND = process.env.JUNGLE_BACKEND ?? "https://api.jungleagents.com"; L14: function parseFlags(argv) { ... L38: function openBrowser(url) { L39: const cmd = process.platform === "darwin" ? "open" : process.platform === "win32" ? "start" : "xdg-open"; L40: try { ... L48: const backend = (flags.backend ?? DEFAULT_BACKEND).replace(/\/$/, ""); L49: const name = flags.name ?? os.hostname(); L50: const existing = await loadConfig();

High

Sandbox Evasion Gated Capability

Source gates dangerous network, credential, or execution behavior behind CI, host, platform, time, or geo fingerprint checks.

dist/cli.jsView on unpkg · L9

Findings

4 High3 Medium5 Low

HighChild Processdist/git.js

HighShell

HighSame File Env Network Executiondist/cli.js

HighSandbox Evasion Gated Capabilitydist/cli.js

MediumNetwork

MediumEnvironment Vars

MediumStructural Risk Force Deep Review

LowNon Install Lifecycle Scripts

LowScripts Present

LowFilesystem

LowHigh Entropy Strings

LowUrl Strings

Source & flagged code

3 flagged

dist/git.jsView file

Lines 1-26javascript

1// GitHub credential handling for the SDK's child git/gh processes.

2// - Write ~/.git-credentials (https://x-access-token:TOKEN@github.com)

3// - Ensure `credential.helper store` in the global gitconfig

4// - Track GH_TOKEN so it can be injected into the SDK `env` for child processes

5// - Optionally clone the configured repo into /workspace/repo

6import { promises as fs } from "node:fs";

7import { spawn } from "node:child_process";

8import os from "node:os";

High

Child Process

Package source references child process execution.

dist/git.jsView on unpkg · L6

9import path from "node:path";

10import { log } from "./log.js";

11const HOME = process.env.HOME ?? os.homedir();

12// Portability (self-hosted): the repo clones inside the workspace (not a hardcoded /workspace), and

13// the credential store is redirectable via JUNGLE_GIT_CREDENTIALS. On a user's own machine the

14// daemon points JUNGLE_GIT_CREDENTIALS + GIT_CONFIG_GLOBAL into the agent's private state dir so the

15// agent never clobbers the person's real ~/.gitconfig / ~/.git-credentials. In a container both are

16// unset and this stays exactly as before (~/.git-credentials, global gitconfig).

17const WORKSPACE = process.env.JUNGLE_WORKSPACE ?? "/workspace";

18const CREDENTIALS_FILE = process.env.JUNGLE_GIT_CREDENTIALS ?? path.join(HOME, ".git-credentials");

19const REPO_DIR = path.join(WORKSPACE, "repo");

20// Latest known token, injected into the SDK env option (see runner.ts).

21let currentToken = null;

22export function getGhToken() {

23 return currentToken;

24}

25function run(cmd, args, opts = {}) {

26 return new Promise((resolve) => {

dist/cli.jsView file

Lines 1-29javascript

1#!/usr/bin/env node

2// `jungle-agents` — the CLI you run on a machine to make it a Jungle "environment". Typical use:

3//

4// jungle-agents connect # authenticate this device (browser), then run the daemon

5//

6// After connecting once you never touch the terminal again: pick this device as an agent's

7// environment in the Jungle web app, and the daemon runs that agent here. `up` re-runs the daemon

8// on a machine that's already connected (e.g. at login / in a service unit).

9import os from "node:os";

10import