New:Introducing Socket Scanning for VS Code Marketplace Extensions.Learn more →
Get Started

@mosadd/bridges

Package Overview
Dependencies
Maintainers
1
Versions
10
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

@mosadd/bridges

EXPERIMENTAL scaffold (not functional yet) — bridge adapter interfaces (Matrix/Discord/Telegram) intended to reach existing networks from mosadd. Every method currently throws BridgeNotImplementedError until real protocol wiring lands. Not for production.

alpha
latest
Source
npmnpm
Version
3.0.0-alpha.28
Version published
Maintainers
1
Created
Source

@mosadd/bridges

Experimental scaffold — NOT shipped, not part of the mosADD product surface. This package is an internal interface stub. The adapters throw BridgeNotImplementedError from every handler — the TypeScript shape is locked, no network is wired, and bridges are not advertised as a mosADD feature. Do not depend on this package. The shipped product is the 4 live m* modules (mDM, mIRC, mURL, mAYL) plus capabilities in @mosadd/mcp.

What this is

A uniform BridgeProvider interface (verifyConfig, sendMessage, listMessages, resolveHandle) kept here so a future contributor has a stable seam to build against. Design-adopted from the Hermes Agent (MIT, Nous Research) gateway/platforms/ pattern — see the project NOTICE for attribution.

import { getBridge, type BridgeProvider } from "@mosadd/bridges";
// every handler currently throws BridgeNotImplementedError

Adding a real provider requires an accepted RFC (see GOVERNANCE.md).

License

Apache-2.0. See LICENSE and NOTICE.

FAQs

Package last updated on 16 Aug 2026

Related posts