You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
-`make nodejsscan` - Run nodejsscan for JS security vulnerabilities
123
124
124
125
**Local-First Security**: Developers are encouraged to run `make pre-commit` and `make test` before every commit, ensuring that security issues are caught and resolved locally before code reaches the repository. This "shift-left" approach means security problems are identified early in the development process, reducing the time and cost of remediation.
125
126
@@ -421,15 +422,17 @@ flowchart TD
421
422
422
423
## 📦 Supported Versions and Security Updates
423
424
424
-
**⚠️ Important**: MCP Gateway is an **OPEN SOURCE PROJECT** provided "as-is" with **NO OFFICIAL SUPPORT** from IBM or its affiliates. Community contributions and best-effort maintenance are provided by project maintainers and contributors.
425
+
**⚠️ Important**: MCP Gateway is an **OPEN SOURCE PROJECT** provided "as-is" with **NO OFFICIAL SUPPORT** from IBM or its affiliates. Community contributions and best-effort maintenance are provided by project contributors.
425
426
426
427
### Version Support Policy
427
428
428
-
- We support **only the latest version** of this project
429
-
- Support is provided **only through the REST API** (not the Admin UI)
430
-
- Admin UI/APIs are provided for developer convenience and **must be disabled in production**
431
-
-**No backports**: Older versions are not maintained or patched
432
-
-**No SLAs**: Security updates are provided on a best-effort basis by the community
429
+
* The **Admin UI** is intended for **localhost-only use** with trusted upstream MCP servers and is **disabled by default** (`MCPGATEWAY_UI_ENABLED=false`)
430
+
* Deployments should use **only the REST APIs**, with proper authentication, **strict input validation and sanitization**, and **downstream output sanitization** as appropriate
431
+
* The REST API is designed to be **accessed by internal services in a trusted environment**, not directly exposed to untrusted end-users
432
+
* Fixes and security improvements are applied **only to the latest `main` branch** - **no backports** are provided
433
+
* The Admin UI and Admin API are intended solely as development conveniences and **must be disabled in production**
434
+
* Bug fixes and security patches are provided on a **best-effort basis**, without SLAs
435
+
* Security hardening efforts prioritize the **REST API**; the Admin UI remains **unsupported**
0 commit comments