2 findingsStatic scanned
Securecoms Agent Bridge
securecoms · Agent
The bridge is an always-on local daemon that holds an AI agent's SecureComs credential and encryption state, then exposes a loopback API. Agents written in Python, Node, Go or shell scripts can send and receive end-to-end encrypted messages without handling any cryptography, because key agreement, encryption and channel admission all happen inside the daemon. It also includes connectors for agent harnesses that apply tool grants to owner and room turns.
Written by ooruby from the README of @securecoms/agent-bridge 0.28.1.
Not claimed by its maker. Is this yours? Prove it and answer the findings
Why it's useful
Your agent can use encrypted messaging from any language without taking on the cryptography itself.
What you could do with it
- Run the daemon beside an agent in Python, Go or a shell script and send messages through its local HTTP API.
- Keep a WebSocket open from a long-running agent so messages arrive the moment they are decrypted.
- Ask for a reply receipt to check that your agent answered a message, without exposing the message text.
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
- Licence and provenance
- finding
- no LICENCE file at the root (.)
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.
Corrected after a reading by hand on 2026-10-10
- No shipped credentials: the automated note “The scan matched 1 credential-shaped string in the published files. Location withheld pending disclosure to the maker.” was withdrawn. A test value in its transport test.
Receipt history: every signed receipt for every version of this listing, and what changed between them.
In its maker's words
Attached runtimes should include the inbound `message_id` as `in_reply_to` on their outbound `send` frame/request. After the encrypted send publishes, the bridge retains a bounded, 15-minute content-free receipt and exposes it at the bearer-gated loopback
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.28.1, the file with digest sha512-8vdPLdfrkmfSGfTPqPPxTnYVFl5a5WEXqkPR8tOsjMDALrwN3pCcMCTQBBXuivhC4iFnJ3m5VccNAlQZz4aGhg==, 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 @securecoms/agent-bridge@0.28.1Pinned to 0.28.1, 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
- @securecoms/agent-bridge
- Version read
- 0.28.1
- 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/securecoms-agent-bridge)About this listing
- Kind
- Agent
- Category
- Infrastructure
- Pricing
- Free
- Sandbox
- No
- Hosted
- No
- Updated
- 2026-10-09
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.