Troubleshooting

Troubleshooting

Plugin install

Marketplace "pandaward" not found The marketplace was not added yet. Run /plugin marketplace add ratomirjovanovic/pandaward first, then /plugin install pandaward-windows@pandaward (Windows) or /plugin install pandaward@pandaward (macOS and Linux).

git@github.com: Permission denied (publickey) while installing An older marketplace definition cloned over SSH when ~/.ssh existed without a GitHub key. The marketplace now clones over HTTPS. Refresh it and install again:

/plugin marketplace update pandaward
/plugin install pandaward-windows@pandaward

If it still fails, remove and add the marketplace again: /plugin marketplace remove pandaward, then /plugin marketplace add ratomirjovanovic/pandaward.

The /pandaward:* commands do not appear Restart Claude Code after installing or updating. /plugin should list the plugin as enabled.

/mcp shows pandaward as failed

• Under Plugin MCPs: run /plugin marketplace update pandaward, reinstall and restart. On macOS and Linux the launcher refuses to run a binary whose checksum does not match bin/SHA256SUMS; reinstalling replaces a damaged download.
• Under Project MCPs with the path .../pandaward/.mcp.json: you opened a checkout of the PandaWard repository from before 0.1.2, or Claude Code still shows a configuration loaded before you pulled. Pull the latest main and restart Claude Code.

Wrong plugin for the platform pandaward@pandaward contains Linux and macOS binaries and a shell launcher; on Windows install pandaward-windows@pandaward instead. Uninstall the wrong one with /plugin uninstall.

Windows: the MCP server does not connect after an update, and /plugin shows an old pandaward-windows Both plugins are installed: pandaward@pandaward (new, but without a Windows binary) and pandaward-windows@pandaward (still on the old version). Keep only the Windows plugin and bring it up to date:

/plugin uninstall pandaward@pandaward
/plugin marketplace update pandaward
/plugin uninstall pandaward-windows@pandaward
/plugin install pandaward-windows@pandaward

Restart Claude Code. /plugin should list only pandaward-windows with the current version, and /mcp should show plugin:pandaward:pandaward as connected. To avoid falling behind again, turn on auto-update for the pandaward marketplace (see Installation).

CLI

project not initialized: run pandaward init first Run pandaward init in the project root. Commands look for .pandaward/ in the current directory and its parents; use --root <dir> to point elsewhere.

invalid .pandaward/config.yaml: ... field xyz not found Since 0.1.2 unknown keys in config.yaml are errors, so a misspelled setting is not silently ignored. Fix or remove the key named in the message. Configuration lists every valid key.

pandaward version prints dev The binary was built from source without a version. Release binaries, plugin installs and go install ...@vX.Y.Z report the real version.

A scanner shows BLOCKED The optional tool is not installed, or it needs network access for advisory data and scan.allow_tool_network is false. pandaward doctor explains each one. A BLOCKED control is a gap, not a pass.

The assessment is INCOMPLETE An adapter failed or timed out. pandaward status and the scan output name the adapter and the reason. Fix it and run pandaward scan again; an incomplete run never counts as clean.

Coverage dropped to zero after editing files Edited files make the affected decisions STALE until you re-scan. Run pandaward retest (or /pandaward:retest).

Network tests

not authorized (exit code 3) There is no valid approval for the current scope.yaml. Any edit to the manifest invalidates the approval, and approvals expire after the hours you chose. Run pandaward scope validate, then pandaward scope approve --by "<your name>" in an interactive terminal. See Network Testing.

An approval made on another machine does not work Approvals are bound to a key in your user configuration directory, so a scope file or ledger copied from somewhere else never counts as approved. Approve again on the machine that runs the test.

Still stuck?

Run pandaward doctor --json and open an issue with the output and the exact error. Do not paste reports or evidence from private projects. Security problems in PandaWard itself go through private reporting.