| Version | Support Status |
|---|---|
| 1.0.x (current) | ✅ Receives security updates |
| < 1.0.0 | ❌ No support |
Do not report security vulnerabilities as public issues.
If you discover a security vulnerability, use GitHub's Private Security Advisories.
Please include:
- Type and impact of the vulnerability
- Steps to reproduce
- Which version(s) of inv_gui are affected
We aim to respond within 72 hours.
inv_gui is a server-side datapack. Keep the following in mind:
-
inv_gui:api/setupshould only be run by operators. It containsforceloadandsetblockcommands; do not expose it to players. -
Listener functions must not cross trust boundaries. Callbacks run in the
@scontext. Be careful before adding commands targeting@aor@e. -
Storage data is server-side only. Do not write untrusted input directly into
inv_gui:datastorage. -
Lock:"InvGui"containers must not be player-accessible. Block player access to coordinates10000 0-2 10000.
Intent-based error detection (i.e. making security decisions based on whether a command succeeded or failed) is not reliable in datapack architecture. inv_gui makes security decisions at configuration time and does not rely on runtime error detection.