3 findingsStatic scanned
Runs OpenAI's Codex coding agent locally on your computer from the command line.
71.3M installs/moApache-2.0
Teamshare Bridge
dominionbanjo · Agent
TeamShare is the coordination hub where agents are registered and given tasks, and teamshare-bridge is the local part that runs them on your computer. A session fetches the task brief with its comments and project files, then drives opencode or Claude, or a built-in headless loop that works with any OpenAI-compatible endpoint, and posts progress and a closing summary back to the task. It needs a TeamShare account and an agent key, plus opencode or Claude installed, or an LLM API key for the headless loop.
Written by ooruby from the README of teamshare-bridge 0.22.15.
Not claimed by its maker. Is this yours? Prove it and answer the findings
Why it's useful
The AI runs on your own computer while TeamShare keeps the tasks, comments and run history in one place.
What you could do with it
- Leave the daemon running so an agent starts work as soon as a task is assigned to it or it is mentioned.
- Run a headless session on any OpenAI-compatible model so the task is split into subtasks that are checked off.
- Watch a session's output live in the TeamShare app's console while the agent works on your machine.
Written from its documentation: what it says it can do, not what our checks found.
Maintenance
Not measuredNo release date is on record for this package yet. The nightly publisher check records one as it reaches each npm package, about once every ten nights.
Release activity only: it says nothing about quality or safety, and a finished small package can be fine without releases. How it is measured
- Command execution is bounded
- inventory
- node child_process (README.md:342)
- node child_process (tools/workspace-arbitration-check.mjs:14)
- synchronous shell execution (tools/workspace-arbitration-check.mjs:303)
- synchronous shell execution (tools/workspace-arbitration-check.mjs:311)
- An inventory of where the code starts another program, not a verdict on this row: whether each one runs a fixed program or whatever it is handed takes a reading by hand.
Published because it was found. A finding is information about where the limits are, not a verdict that the software is unsafe.
What this does not cover
- Everything. Treat it as you would software from anywhere else.
Receipt history: every signed receipt for every version of this listing, and what changed between them.
In its maker's words
Local bridge for TeamShare agents - CLI session runner, auto-wake WebSocket daemon, and teamshare:// protocol handler.
Compare with
Compare all 4How far this has been checked
Static scanned
- What it establishes
- Its published package, or for a hosted server its source repository at a recorded commit, was read file by file, without running it, by every check in our current scan.
- What it does not
- How it behaves when it runs, or anything the scan does not read yet: several rubric checks, the repository's history, and compiled code in folders named dist or build. For a hosted server, that the endpoint runs the code that was read. The ooruby Index sets out exactly what was read.
- Exactly what was read
- Version 0.22.15, the file with digest sha512-lLZlpdcLM+CQBo3i171vFMjrCavTKXoE0+QAWA0i5TXuEXoNnsB8aDAQdTXIFrsSBjeyX3EByTUAJdnpXG/uGA==, as the registry publishes it. A published version cannot be replaced, so this names the same bytes for anyone who checks.
- Authentication
- Runs locally. No hosted endpoint is listed for this package. You run it on your own machine, so there is no endpoint of ours to authenticate against.
Adding it
Run it with:
npx -y -p teamshare-bridge@0.22.15 teamshare-agentPinned to 0.22.15, which is the version the findings above were found in. Drop the version to take whatever is newest, and the report on this page stops describing what you installed.
Where this came from
- Registry
- npm
- Package
- teamshare-bridge
- Version read
- 0.22.15
- Resolved
- 2026-10-10
No build provenance published. The repository above is the one the publisher declared, and nothing links it to the package you would install. That is not a mark against this listing, since most packages are published this way, but it is a check nobody can run.
The badge, if this is your listing
It renders the current rung (static scanned) and links back here, where what that does and does not establish is one click away. It updates itself as the evidence deepens.
[](https://ooruby.com/market/teamshare-bridge)About this listing
- Kind
- Agent
- Category
- Developer tools
- Pricing
- Free
- Sandbox
- No
- Hosted
- No
- Updated
- 2026-10-08
Similar agents
All agentsVerification records what our published tests found on a specific version at a specific date. It is not a warranty, and it does not certify that software is free of defects.