Commands

Commands #

All commands require the pluginguard.admin permission (default: server operators). Console always has access regardless of permissions.

CommandWhat it does
/pluginguard scanScans every jar in plugins/ and reports every finding, sorted worst-first. In-game chat shows the first 20 findings, the console and the saved report show all of them.
/pluginguard info <name>Shows every fact PluginGuard extracted about one plugin jar, and the findings about it. Matches the jar file name or the plugin name (exact match first, then partial).
/pluginguard fixlist [all]Numbered list of what needs fixing from the last scan: critical findings, or with all warnings as well.
/pluginguard ignore <code> [plugin]Hides a finding you reviewed, from the next scan on. ignore list shows all rules, /pluginguard unignore <code> [plugin] removes one. Rules are stored in ignored.txt; config.yml is never rewritten. Each finding in chat ends with its code in grey.
/pluginguard export <format>Re-exports the most recent scan's report in a different format without re-scanning. Formats: txt, json, yaml, md, html.
/pluginguard reloadReloads config.yml (and the active language file) without restarting the server.
/pluginguard helpShows this command list in-game.

Alias: /pguard.

Reading a report #

Every finding has a severity:

  • CRITICAL - this plugin will fail to enable, or will crash/throw at runtime. Fix before your next restart.
  • WARNING - it will probably still run, but something about it is likely to misbehave under some condition, or is worth a second look.
  • INFO - purely advisory. No functional risk, just something you might want to know.