@guardbee/security-suite@0.4.1

Patch Changes

• Updated dependencies [103a94b]:
  • @guardbee/mcp-oauth-auditor@0.3.0
  • @guardbee/mcp-owasp-scan@0.3.3

@guardbee/security-suite@0.4.0

Minor Changes

• #189 d6b75fe Thanks @4hmetuyar! - - Node 22 for the proxy, document-scanner and security-suite (engines.node: ">=22"): ldapts 9 and unpdf, which they depend on, require it. Node 18 and 20 are past end of life; the other packages still run on Node 18.
  • require() works for every ESM package: each exports entry gains a default condition next to import (Node 20.19+ / 22.12+ can require() ESM), so require("@guardbee/mcp-secret-scanner") no longer fails with ERR_PACKAGE_PATH_NOT_EXPORTED.
  • guardbee-proxy --help / --version print usage and the version instead of failing with "No proxy target configured"; guardbee-gateway --help / --version no longer start the stdio server, and an unknown argument is an error.
  • The proxy's npm description starts with "MCP security gateway" again.

Patch Changes

• Updated dependencies [d6b75fe]:
  • @guardbee/mcp-a2a-auditor@0.2.2
  • @guardbee/mcp-agent-graph-auditor@0.2.2
  • @guardbee/mcp-ai-code-scanner@0.4.2
  • @guardbee/mcp-audit-gap-auditor@0.3.2
  • @guardbee/mcp-compliance-checker@0.3.2
  • @guardbee/mcp-context-oversharing-auditor@0.3.2
  • @guardbee/mcp-dependency-auditor@0.7.2
  • @guardbee/mcp-dns-intelligence@0.9.2
  • @guardbee/mcp-document-scanner@0.3.0
  • @guardbee/mcp-elicitation-auditor@0.2.2
  • @guardbee/mcp-llm-redteam@0.2.2
  • @guardbee/mcp-config-auditor@0.6.2
  • @guardbee/mcp-server-auditor@0.2.2
  • @guardbee/mcp-memory-poisoning-scanner@0.2.2
  • @guardbee/mcp-model-scanner@0.2.2
  • @guardbee/mcp-oauth-auditor@0.2.2
  • @guardbee/mcp-owasp-scan@0.3.2
  • @guardbee/mcp-prompt-injection-scanner@1.0.2
  • @guardbee/mcp-prompt-leak-scanner@1.0.2
  • @guardbee/mcp-rug-pull-detector@0.3.2
  • @guardbee/mcp-secret-scanner@1.0.2
  • @guardbee/mcp-slopsquat-scanner@0.2.2
  • @guardbee/mcp-ssl-inspector@0.4.2
  • @guardbee/mcp-threat-rules@0.4.2
  • @guardbee/mcp-tool-poisoning-scanner@0.3.2
  • @guardbee/mcp-toxic-flow-auditor@1.0.2
  • @guardbee/mcp-unbounded-consumption-auditor@0.2.2
  • @guardbee/mcp-vector-store-scanner@0.2.2
  • @guardbee/mcp-vulnerability-scanner@0.3.2

@guardbee/security-suite@0.3.1

Patch Changes

• #185 12487ab Thanks @4hmetuyar! - mcp-security-proxy and mcp-db-gateway get an exports map (the package root, ./dist/* for existing deep imports, package.json); db-gateway also exports ./adapters/*, so the documented import { createPrismaAdapter } from "@guardbee/mcp-db-gateway/adapters/prisma" now resolves. The proxy moves to ldapts 9 (its older uuid had an advisory). The telemetry package description now says opt-in, the suite's starts with "MCP security suite", and document-scanner's homepage is its README.

• #178 c89dc93 Thanks @4hmetuyar! - MCP tools are registered with server.registerTool(name, { description, inputSchema, annotations }, handler) instead of the deprecated server.tool(...) (132 registrations, no change to tool names, descriptions or parameters). @modelcontextprotocol/sdk is now required at ^1.30.0 instead of ^1.0.0 / >=1.0.0, so an install cannot resolve an old SDK the code was never tested with. @guardbee/mcp-telemetry's instrumentServer wraps registerTool as well as tool.

• #175 341a283 Thanks @4hmetuyar! - Smaller npm packages (55% less unpacked in total; the proxy 944 → 513 kB): source maps and compiled tests are no longer published (the sources they point at never were), and the translated READMEs stay on GitHub, linked from the English one. Package descriptions now start with what people search for ("MCP gateway and LLM firewall", "Secret scanner for code, git history and AI agent transcripts") and carry more search keywords.

• Updated dependencies [ee8718b, 12487ab, c89dc93, 341a283]:

  • @guardbee/mcp-toxic-flow-auditor@1.0.1
  • @guardbee/mcp-tool-poisoning-scanner@0.3.1
  • @guardbee/mcp-server-auditor@0.2.1
  • @guardbee/mcp-audit-gap-auditor@0.3.1
  • @guardbee/mcp-unbounded-consumption-auditor@0.2.1
  • @guardbee/mcp-ai-code-scanner@0.4.1
  • @guardbee/mcp-telemetry@0.3.0
  • @guardbee/mcp-document-scanner@0.2.1
  • @guardbee/mcp-a2a-auditor@0.2.1
  • @guardbee/mcp-agent-graph-auditor@0.2.1
  • @guardbee/mcp-compliance-checker@0.3.1
  • @guardbee/mcp-context-oversharing-auditor@0.3.1
  • @guardbee/mcp-dependency-auditor@0.7.1
  • @guardbee/mcp-dns-intelligence@0.9.1
  • @guardbee/mcp-elicitation-auditor@0.2.1
  • @guardbee/mcp-llm-redteam@0.2.1
  • @guardbee/mcp-config-auditor@0.6.1
  • @guardbee/mcp-memory-poisoning-scanner@0.2.1
  • @guardbee/mcp-model-scanner@0.2.1
  • @guardbee/mcp-oauth-auditor@0.2.1
  • @guardbee/mcp-owasp-scan@0.3.1
  • @guardbee/mcp-prompt-injection-scanner@1.0.1
  • @guardbee/mcp-prompt-leak-scanner@1.0.1
  • @guardbee/mcp-rug-pull-detector@0.3.1
  • @guardbee/mcp-secret-scanner@1.0.1
  • @guardbee/mcp-slopsquat-scanner@0.2.1
  • @guardbee/mcp-ssl-inspector@0.4.1
  • @guardbee/mcp-threat-rules@0.4.1
  • @guardbee/mcp-vector-store-scanner@0.2.1
  • @guardbee/mcp-vulnerability-scanner@0.3.1

@guardbee/security-suite@0.3.0

Minor Changes

• #172 9ae575f Thanks @4hmetuyar! - security-suite now covers every GuardBee scanner and auditor (29 packages, 124 MCP tools). guardbee serve serves the recommended group by default (owasp-scan, secret-scanner, prompt-injection-scanner, toxic-flow-auditor, mcp-config-auditor, dependency-auditor: 31 tools); --tools= (or GUARDBEE_SUITE_TOOLS) takes groups (code, supply-chain, network, platform, all) and package ids. Tool names carry their package's prefix (secrets_scan_text, injection_scan_text) so packages do not collide. guardbee <package-id> <args> runs any package's CLI and guardbee list lists them; the old secret-scan, dep-audit, ssl-inspect and dns-check shortcuts still work. With no arguments and no terminal on stdin (an MCP client starting it), the suite now serves instead of printing help, and its MCP Registry entry passes serve.

  Breaking for guardbee serve users: the five plain tool names (scan_directory, scan_file, audit_dependencies, inspect_ssl, check_dns) are now prefixed package tools; see "Upgrading from 0.2" in the README.

  Every scanner and auditor package exports registerTools(server), which registers its MCP tools on a given McpServer; startServer() uses it.

Patch Changes

• #170 c71f728 Thanks @4hmetuyar! - Package hygiene: every package now ships its LICENSE and CHANGELOG.md, and has a homepage (its guardbee.ai page), a bugs link, engines.node and the guardbee, mcp and security keywords. READMEs gain npm badges and a feedback section pointing to GitHub Discussions; the owasp-scan README documents every mode, option, MCP tool and the OWASP coverage.

  Telemetry is now opt-in. Nothing is sent unless GUARDBEE_TELEMETRY=1 (or true/on/yes) is set; GUARDBEE_TELEMETRY=0 is no longer needed. When it is on, the one-time stderr notice says what is sent and to which endpoint.

• Updated dependencies [c71f728, c3b71f8, 9ae575f]:

  • @guardbee/mcp-a2a-auditor@0.2.0
  • @guardbee/mcp-agent-graph-auditor@0.2.0
  • @guardbee/mcp-ai-code-scanner@0.4.0
  • @guardbee/mcp-audit-gap-auditor@0.3.0
  • @guardbee/mcp-compliance-checker@0.3.0
  • @guardbee/mcp-context-oversharing-auditor@0.3.0
  • @guardbee/mcp-dependency-auditor@0.7.0
  • @guardbee/mcp-dns-intelligence@0.9.0
  • @guardbee/mcp-document-scanner@0.2.0
  • @guardbee/mcp-elicitation-auditor@0.2.0
  • @guardbee/mcp-llm-redteam@0.2.0
  • @guardbee/mcp-config-auditor@0.6.0
  • @guardbee/mcp-server-auditor@0.2.0
  • @guardbee/mcp-memory-poisoning-scanner@0.2.0
  • @guardbee/mcp-model-scanner@0.2.0
  • @guardbee/mcp-oauth-auditor@0.2.0
  • @guardbee/mcp-owasp-scan@0.3.0
  • @guardbee/mcp-prompt-injection-scanner@1.0.0
  • @guardbee/mcp-prompt-leak-scanner@1.0.0
  • @guardbee/mcp-rug-pull-detector@0.3.0
  • @guardbee/mcp-secret-scanner@1.0.0
  • @guardbee/mcp-slopsquat-scanner@0.2.0
  • @guardbee/mcp-ssl-inspector@0.4.0
  • @guardbee/mcp-threat-rules@0.4.0
  • @guardbee/mcp-tool-poisoning-scanner@0.3.0
  • @guardbee/mcp-toxic-flow-auditor@1.0.0
  • @guardbee/mcp-unbounded-consumption-auditor@0.2.0
  • @guardbee/mcp-vector-store-scanner@0.2.0
  • @guardbee/mcp-vulnerability-scanner@0.3.0
  • @guardbee/mcp-telemetry@0.2.0

@guardbee/ner@0.1.6

Patch Changes

• #175 341a283 Thanks @4hmetuyar! - Smaller npm packages (55% less unpacked in total; the proxy 944 → 513 kB): source maps and compiled tests are no longer published (the sources they point at never were), and the translated READMEs stay on GitHub, linked from the English one. Package descriptions now start with what people search for ("MCP gateway and LLM firewall", "Secret scanner for code, git history and AI agent transcripts") and carry more search keywords.
• Updated dependencies [341a283]:
  • @guardbee/guard-core@1.0.1

@guardbee/ner@0.1.5

Patch Changes

• #170 c71f728 Thanks @4hmetuyar! - Package hygiene: every package now ships its LICENSE and CHANGELOG.md, and has a homepage (its guardbee.ai page), a bugs link, engines.node and the guardbee, mcp and security keywords. READMEs gain npm badges and a feedback section pointing to GitHub Discussions; the owasp-scan README documents every mode, option, MCP tool and the OWASP coverage.

  Telemetry is now opt-in. Nothing is sent unless GUARDBEE_TELEMETRY=1 (or true/on/yes) is set; GUARDBEE_TELEMETRY=0 is no longer needed. When it is on, the one-time stderr notice says what is sent and to which endpoint.

• Updated dependencies [c71f728, c3b71f8]:

  • @guardbee/guard-core@1.0.0

@guardbee/mcp-vulnerability-scanner@0.3.2

Patch Changes

• #189 d6b75fe Thanks @4hmetuyar! - - Node 22 for the proxy, document-scanner and security-suite (engines.node: ">=22"): ldapts 9 and unpdf, which they depend on, require it. Node 18 and 20 are past end of life; the other packages still run on Node 18.
  • require() works for every ESM package: each exports entry gains a default condition next to import (Node 20.19+ / 22.12+ can require() ESM), so require("@guardbee/mcp-secret-scanner") no longer fails with ERR_PACKAGE_PATH_NOT_EXPORTED.
  • guardbee-proxy --help / --version print usage and the version instead of failing with "No proxy target configured"; guardbee-gateway --help / --version no longer start the stdio server, and an unknown argument is an error.
  • The proxy's npm description starts with "MCP security gateway" again.

@guardbee/mcp-vulnerability-scanner@0.3.1

Patch Changes

• #178 c89dc93 Thanks @4hmetuyar! - MCP tools are registered with server.registerTool(name, { description, inputSchema, annotations }, handler) instead of the deprecated server.tool(...) (132 registrations, no change to tool names, descriptions or parameters). @modelcontextprotocol/sdk is now required at ^1.30.0 instead of ^1.0.0 / >=1.0.0, so an install cannot resolve an old SDK the code was never tested with. @guardbee/mcp-telemetry's instrumentServer wraps registerTool as well as tool.

• #175 341a283 Thanks @4hmetuyar! - Smaller npm packages (55% less unpacked in total; the proxy 944 → 513 kB): source maps and compiled tests are no longer published (the sources they point at never were), and the translated READMEs stay on GitHub, linked from the English one. Package descriptions now start with what people search for ("MCP gateway and LLM firewall", "Secret scanner for code, git history and AI agent transcripts") and carry more search keywords.

• Updated dependencies [12487ab, c89dc93, 341a283]:

  • @guardbee/mcp-telemetry@0.3.0

@guardbee/mcp-vulnerability-scanner@0.3.0

Minor Changes

• #172 9ae575f Thanks @4hmetuyar! - security-suite now covers every GuardBee scanner and auditor (29 packages, 124 MCP tools). guardbee serve serves the recommended group by default (owasp-scan, secret-scanner, prompt-injection-scanner, toxic-flow-auditor, mcp-config-auditor, dependency-auditor: 31 tools); --tools= (or GUARDBEE_SUITE_TOOLS) takes groups (code, supply-chain, network, platform, all) and package ids. Tool names carry their package's prefix (secrets_scan_text, injection_scan_text) so packages do not collide. guardbee <package-id> <args> runs any package's CLI and guardbee list lists them; the old secret-scan, dep-audit, ssl-inspect and dns-check shortcuts still work. With no arguments and no terminal on stdin (an MCP client starting it), the suite now serves instead of printing help, and its MCP Registry entry passes serve.

  Breaking for guardbee serve users: the five plain tool names (scan_directory, scan_file, audit_dependencies, inspect_ssl, check_dns) are now prefixed package tools; see "Upgrading from 0.2" in the README.

  Every scanner and auditor package exports registerTools(server), which registers its MCP tools on a given McpServer; startServer() uses it.

Patch Changes

• #170 c71f728 Thanks @4hmetuyar! - Package hygiene: every package now ships its LICENSE and CHANGELOG.md, and has a homepage (its guardbee.ai page), a bugs link, engines.node and the guardbee, mcp and security keywords. READMEs gain npm badges and a feedback section pointing to GitHub Discussions; the owasp-scan README documents every mode, option, MCP tool and the OWASP coverage.

  Telemetry is now opt-in. Nothing is sent unless GUARDBEE_TELEMETRY=1 (or true/on/yes) is set; GUARDBEE_TELEMETRY=0 is no longer needed. When it is on, the one-time stderr notice says what is sent and to which endpoint.

• Updated dependencies [c71f728]:

  • @guardbee/mcp-telemetry@0.2.0

@guardbee/mcp-vector-store-scanner@0.2.2

Patch Changes

• #189 d6b75fe Thanks @4hmetuyar! - - Node 22 for the proxy, document-scanner and security-suite (engines.node: ">=22"): ldapts 9 and unpdf, which they depend on, require it. Node 18 and 20 are past end of life; the other packages still run on Node 18.
  • require() works for every ESM package: each exports entry gains a default condition next to import (Node 20.19+ / 22.12+ can require() ESM), so require("@guardbee/mcp-secret-scanner") no longer fails with ERR_PACKAGE_PATH_NOT_EXPORTED.
  • guardbee-proxy --help / --version print usage and the version instead of failing with "No proxy target configured"; guardbee-gateway --help / --version no longer start the stdio server, and an unknown argument is an error.
  • The proxy's npm description starts with "MCP security gateway" again.