osborn@0.9.156
Voice AI coding assistant - local agent that connects to Osborn frontend
AI Security Review
scanned 1mo ago · by lpm-firewall-aiInspected sources show a real Voice AI coding assistant with no consumer install hook, but the CLI runtime still pipes a remote install script into a shell, reads Claude session files, and ships a skill that overwrites agent instructions from the network. Incomplete static parse coverage plus that dual-use runtime keep this at a warning rather than a publish block or a clean mark.
Decision evidence
public snapshot- When the user starts the IDE, dist/index.js pipes https://code-server.dev/install.sh into sh.
- code-server is spawned with authentication disabled and proxied through the agent HTTP server.
- dist/session-access.js reads full Claude session JSONL and related artifacts under ~/.claude.
- bin/cli.js launches dist/index.js with the inherited process environment.
- A bundled skill tells the agent to overwrite ~/.claude/skills from https://www.voice-native.com/api/sync-skill.
- Background Claude slots run with permissionMode bypassPermissions.
- package.json has no preinstall, install, or postinstall; prepublishOnly only runs the publisher build.
- The package is a user-invoked Voice AI coding assistant CLI, not a library that runs on import.
- Network calls target LiveKit, OpenAI, Groq, Recall.ai, Smithery, and the product frontend rather than a hidden drop host.
- Scanner env-plus-network-plus-spawn flags sit in the same agent runtime because that is the product, not a hidden harvest path.
- Copying process.env into child Claude and code-server processes is local spawn wiring, not a POST of secrets to a third party.
Source & flagged code
9 flagged · loading sourcePackage source references dynamic require/import behavior.
dist/jsonl-search.jsView on unpkg · L34Findings
Affected versions and remediation
This report applies to osborn@0.9.156.
See all versions of osborn for other recorded verdicts.
- Review the evidence and your use of osborn@0.9.156 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.