The official command-line interface for CapiscIO, the Agent-to-Agent (A2A) validation platform.

This package provides a convenient Node.js distribution for the CapiscIO CLI. It acts as a smart wrapper that automatically manages the underlying capiscio-core binary (written in Go), ensuring you always have the correct executable for your operating system and architecture.

Note: This is a wrapper. The core logic resides in capiscio-core.

npm install -g capiscio

Once installed, the capiscio command is available in your terminal. It passes all arguments directly to the core binary.

# Validate an agent card
capiscio validate ./agent-card.json

# Validate with JSON output
capiscio validate https://my-agent.example.com --json

# Issue a self-signed badge (development)
capiscio badge issue --self-sign --sub did:web:example.com:agents:my-agent

# Verify a badge (offline mode)
capiscio badge verify "eyJhbGciOiJFZERTQSJ9..." --offline

# Check version
capiscio --version

# Get help
capiscio --help

The Node.js wrapper includes specific commands to manage the binary:

1. Detection: When you run capiscio, the script detects your OS (Linux, macOS, Windows) and Architecture (AMD64, ARM64).
2. Provisioning: It checks if the correct capiscio-core binary is present:
   • Primary: <package>/bin/capiscio (alongside node_modules)
   • Fallback: ~/.capiscio/bin/capiscio (if package dir is read-only)
   • Windows fallback: %USERPROFILE%\.capiscio\bin
3. Download: If missing, it downloads the release from GitHub on first run (no postinstall script).
4. Execution: It seamlessly delegates to the Go binary, passing all arguments through.

• macOS: AMD64 (Intel), ARM64 (Apple Silicon)
• Linux: AMD64, ARM64
• Windows: AMD64

On first run, the wrapper downloads the capiscio-core binary and verifies its SHA-256 checksum against the published checksums.txt from the GitHub release.

If verification fails or the checksums file is unavailable:

# Temporary bypass (not recommended for production)
export CAPISCIO_SKIP_CHECKSUM=true

"Permission denied" errors: Ensure your user has write access to the cache directory. You can reset the cache by running:

capiscio --wrapper-clean

"Binary not found" or download errors: If you are behind a corporate firewall, ensure you can access github.com.

Checksum verification failures: If you see "Checksum verification failed", the binary integrity could not be confirmed. This can happen with pre-release versions or network issues. See the Binary Integrity Verification section above.

• capiscio - Python CLI wrapper (identical functionality)
• capiscio-sdk-python - Python SDK for programmatic usage
• capiscio-core - Go core engine

Apache-2.0