ArgusGate v0.1.4

Fixed

• Redacted secret-like server IDs, tool names, finding locations, server summaries, and tool summaries in JSON reports.
• Redacted the full URL userinfo segment so token-like usernames in user:password@host URLs do not leak.
• Detected URL userinfo credentials such as https://user:password@example.test as secret exposure findings.
• Rejected invalid MCP config and fixture shapes instead of silently scanning empty server or tool objects.
• Matched Windows drive paths in policy path rules.
• Detected host system administration capabilities such as systemctl, launchctl, scheduled tasks, registry operations, firewall operations, and privileged host operations.
• Reduced SQL false positives when metadata says write statements are blocked, rejected, forbidden, disallowed, prohibited, or prevented.

Verification

• go test ./...
• go vet ./...
• go build -o .\bin\argusgate.exe .\cmd\argusgate
• argusgate --help
• argusgate --version
• argusgate policy validate --policy examples/policies/default.yaml
• argusgate fixtures scan --path examples/fixtures/safe-tools.yaml --policy examples/policies/default.yaml
• argusgate fixtures scan --path examples/fixtures/malicious-tools.yaml --policy examples/policies/default.yaml
• invalid fixture scan exits 2 with a field-level parser error
• URL userinfo credential fixture reports AG-SE010 without leaking fake credentials in JSON