@tonbo/yield@0.3.20
Tonbo Yield: capture your agents' sessions on every machine and list them from any.
AI Security Review
scanned 1d ago · by lpm-firewall-aiThe source automatically sends runtime usage telemetry with session and handoff identifiers, and the package provides only an environment-variable opt-out without an in-package disclosure. The credential-looking strings are fake redaction-test data, and I found no credential redirection or install-time attack.
Decision evidence
public snapshot- On the first turn after a handoff, the capture hook automatically records a timing metric and includes the session ID and handoff ID.
- Metrics are enabled by default; they can be disabled with TONBO_YIELD_METRICS=off.
- The metric is POSTed to /yield/metrics through the API, whose default host is api.tonbo.dev.
- The manifest describes a session-capture CLI and declares no install lifecycle hook.
- The apparent OpenAI and Anthropic secret strings occur in a redaction test fixture that explicitly says its secrets are fake.
- The metric contains a timing value and service-generated identifiers, not session contents or credential values.
- The package’s stated purpose is capturing and listing agent sessions.
- No install-time behavior was identified.
Source & flagged code
5 flaggedPackage contains a critical-looking secret pattern.
dist/bin/yield.jsView on unpkg · L3790GitHub personal access token in dist/bin/yield.js
dist/bin/yield.jsView on unpkg · L3790Manifest-reachable source sends a prompted API credential to a fixed unofficial gateway and persists the redirection.
Findings
Affected versions and remediation
This report applies to @tonbo/yield@0.3.20.
See all versions of @tonbo/yield for other recorded verdicts.
- Review the evidence and your use of @tonbo/yield@0.3.20 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.