registry / @tonbo/yield / 0.1.3
@tonbo/yield@0.1.3
Tonbo Yield: capture your agents' sessions on every machine and list them from any.
AI Security Review
scanned 5d ago · by lpm-firewall-aiThe reviewed runtime behavior matches the package's stated purpose: capturing agent sessions and sending them to Tonbo using its login and service APIs. No install hook or unrelated gated behavior was identified in the inspected entry point and credential flows.
Static reason
One or more suspicious static signals were detected.
Trigger
User runs CLI commands; background capture begins only after the user installs or runs the daemon.
Impact
Expected session capture and access to the user's Tonbo account; no unrelated collection or gated malicious behavior was found.
Mechanism
Uses Tonbo login and service APIs with exchanged tokens to upload captured session data.
AI rationale
The reviewed runtime behavior matches the package's stated purpose: capturing agent sessions and sending them to Tonbo using its login and service APIs. No install hook or unrelated gated behavior was identified in the inspected entry point and credential flows.
Network endpoints4
tonbo.devapi.tonbo.devstreams.tonbo.devgit.tonbo.dev
Decision evidence
public snapshotAI called this Clean at 90.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The manifest describes a session-capture CLI and declares no install lifecycle hook.
- The CLI performs its login handoff through the Tonbo login origin using PKCE.
- Session upload requests use the configured service origin and an exchanged access token.
- Installing the background capture service requires an explicit `yield daemon install` command.
- The executable parses user-supplied CLI arguments at startup.
Evidence against
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetwork
HighEntropyStringsUrlStrings
Source & flagged code
5 flaggeddist/bin/yield.jsView file
9import { createHash, randomBytes } from "node:crypto";
L10: import { createServer } from "node:http";
L11: import { execFile } from "node:child_process";
L12: import os2 from "node:os";
...
L24: title: "You are signed in.",
L25: body: "Return to your terminal. This tab can be closed."
L26: },
...
L166: const response = await fetcher(url, init);
L167: const body = await response.json().catch(() => null);
L168: if (response.ok)
...
L818: var REFUSED_MODE_BITS = Number.parseInt(credentialsContract.reader.refuse_mode_bits, 8);
L819: function defaultCredentialsPath(env = process.env) {
High
Sandbox Evasion Gated Capability
Source gates dangerous network, credential, or execution behavior behind CI, host, platform, time, or geo fingerprint checks.
dist/bin/yield.jsView on unpkg · L91061const authorization = new URL("/cli/login", this.loginOrigin);
authorization.search = new URLSearchParams({
code_challenge: challenge,
code_challenge_method: "S256",
redirect_uri: redi
Low
Ai Review Evidence
The CLI performs its login handoff through the Tonbo login origin using PKCE.
dist/bin/yield.jsView on unpkg · L10614649const url = `${this.deps.origin}${repoCreatePath(target.workspace, name)}`;
const response = await this.deps.tokens.send(
target.key,
(token) => this.deps.fetch(url, {
method: "PUT",
r
Findings
1 High3 Medium8 Low
HighSandbox Evasion Gated Capabilitydist/bin/yield.js
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
LowSuspicious Lifecycle Evidencepackage.json
LowAi Review Evidencedist/bin/yield.js
LowAi Review Evidencedist/bin/yield.js
LowAi Review Evidencedist/bin/yield.js
Affected versions and remediation
This report applies to @tonbo/yield@0.1.3.
See all versions of @tonbo/yield for other recorded verdicts.
- Review the evidence and your use of @tonbo/yield@0.1.3 before allowing it. Restrict the permissions described in this report.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.