registry / @tonbo/yield / 0.4.1
@tonbo/yield@0.4.1
Tonbo Yield: capture your agents' sessions on every machine and list them from any.
AI Security Review
scanned 1d ago · by lpm-firewall-aiThe manifest has no install hook, and the reviewed API flow sends the Tonbo credential to the Tonbo management API. The flagged OpenAI and Anthropic patterns occur in redaction fixtures; no code reading those provider credentials or redirecting them was found.
Static reason
One or more suspicious static signals were detected.
Trigger
The CLI runs when a user invokes the yield command.
Impact
No unauthorized credential forwarding or other malicious behavior was found in the reviewed source.
Mechanism
The inspected credential flow uses the Tonbo management API; the suspected third-party API keys appear only in redaction test data.
AI rationale
The manifest has no install hook, and the reviewed API flow sends the Tonbo credential to the Tonbo management API. The flagged OpenAI and Anthropic patterns occur in redaction fixtures; no code reading those provider credentials or redirecting them was found.
Network endpoints2
api.tonbo.devyield.tonbo.io/install.sh
Decision evidence
public snapshotAI called this Clean at 94.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The manifest exposes dist/bin/yield.js as the CLI and declares no install lifecycle script.
- The CLI's management API uses https://api.tonbo.dev as its default origin.
- The management API sends its bearer credential to a URL built from that configured origin.
- The apparent OpenAI key is in a redaction test fixture, not code that reads the environment variable.
Evidence against
- The bundle references a curl-to-shell upgrade command, but the inspected source shows it as a command string for status repair, not an install hook.
- The CLI reads TONBO_API_KEY, which is the credential for the package's own Tonbo service.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetwork
HighEntropyStringsUrlStrings
Source & flagged code
6 flaggeddist/bin/yield.jsView file
5312patternName = github_pat
severity = critical
line = 5312
Critical
Critical Secret
Package contains a critical-looking secret pattern.
dist/bin/yield.jsView on unpkg · L53125312patternName = github_pat
severity = critical
line = 5312
Critical
Secret Pattern
GitHub personal access token in dist/bin/yield.js
dist/bin/yield.jsView on unpkg · L5312•Manifest-reachable source captures an API credential, sends it to a fixed unofficial gateway, and persists that redirection in agent or shell configuration.
dist/bin/yield.js:
import { mkdir as mkdir15, readFile as readFile23, stat as stat10, writeFile as writeFile6 } from "node:fs/promises";
import { createInterface as createInterface2 } from "node:readline/promises";
"description": "Where a client takes its credential, first match wins. A library takes an explicit option first; the CLIs have none. `env` is an API key of one account (TONBO_API_K...
headers: { authorization: `Bearer ${key}`, "content-type": "application/json" },
const headers = { authorization: `Bearer ${key}` };
await handle.writeFile(`${JSON.stringify(value, null, 2)}
await handle.writeFile(JSON.stringify(record3));
auth
High
Findings
2 Critical1 High2 Medium7 Low
CriticalCritical Secretdist/bin/yield.js
CriticalSecret Patterndist/bin/yield.js
HighCredential Redirect Persistencedist/bin/yield.js
MediumNetwork
MediumEnvironment Vars
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
LowSuspicious Lifecycle Evidencepackage.json
LowAi Review Evidencedist/bin/yield.js
LowAi Review Evidencedist/bin/yield.js
Affected versions and remediation
This report applies to @tonbo/yield@0.4.1.
See all versions of @tonbo/yield for other recorded verdicts.
- Review the evidence and your use of @tonbo/yield@0.4.1 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.