@weave_protocol/full

🕸️ @weave_protocol/full

The complete Weave Protocol security suite — one install.

npm install @weave_protocol/full

That's it. You now have every Weave Protocol package installed:

Package	What it does
🛡️ @weave_protocol/mund	Security scanner — secrets, PII, injection, MCP vetting, threat intel
🏛️ @weave_protocol/hord	Encrypted vault with Yoxallismus cipher
⚖️ @weave_protocol/domere	Compliance (SOC2/HIPAA/PCI-DSS/GDPR/CCPA) + blockchain anchoring
👥 @weave_protocol/witan	Multi-agent consensus & governance
🔍 @weave_protocol/hundredmen	Real-time MCP proxy with drift detection
🛂 @weave_protocol/tollere	Supply chain security — npm, Docker, IDE extensions
🔗 @weave_protocol/langchain	LangChain.js security callbacks
🔌 @weave_protocol/api	REST API + monitoring dashboard

Usage

You can import from the bundle:

import { mund, hord, tollere } from '@weave_protocol/full';

const scan = await mund.scan("My API key is sk-1234...");
const risk = await tollere.scanPackage("axios", "1.7.2");

Or from individual packages — same effect:

import { scan } from '@weave_protocol/mund';
import { scanPackage } from '@weave_protocol/tollere';

Want a guided setup?

For framework detection, scaffolding, and config generation, use @weave_protocol/cli:

npx @weave_protocol/cli init

It detects whether you're using LangChain, LlamaIndex, MCP, OpenAI, or Anthropic SDKs and scaffolds the right security middleware for your stack.

Why a bundle?

Some users want to evaluate the whole suite or build something that uses several packages together. Installing everything via one dependency keeps package.json clean and ensures version compatibility across the suite.

If you only need a few packages, install them individually — the bundle is purely additive.

License

Apache 2.0 — See LICENSE