opena2a status

Display aggregated security status for the current project.

Usage

opena2a status [options]

Description

Collects and displays the security posture of the current project by aggregating data from multiple sources: Shield initialization state, ConfigGuard signed file integrity, and identity registration status. Each component reports its current state (active, inactive, or not configured), policy enforcement mode, and integrity status.

Status Components

ComponentDetails
ShieldInitialization state, active protections, and overall status.
ConfigGuardNumber of signed files, tampered files, and policy mode.
IdentityLocal identity presence, registration status, and trust score.

Flags

FlagDescription
--dir <path>Target directory (default: current directory).
--format <text|json>Output format.
--ciCI mode with deterministic output.
--verboseShow detailed status for each component.

Examples

# Show project security status
opena2a status
# JSON output for scripting
opena2a status --format json
# Verbose status of a specific directory
opena2a status --dir ./my-agent --verbose

What It Shows

The status command provides a single-glance overview of your project security configuration by checking three subsystems. Each subsystem reports independently, so you can quickly identify which areas are configured and which need attention.

  • Shield -- Whether the security orchestration layer is initialized, what protections are active (event log, policy engine, session tracking, LLM analysis), and the overall operational mode (monitor, enforce, or disabled).
  • ConfigGuard -- The number of configuration files that have been signed, whether any signed files show tampering (hash mismatch), and the current policy mode (warn or block).
  • Identity -- Whether a local Ed25519 identity exists, whether it has been registered with the Trust Registry, and the current trust score if registered.

Expected Output

$ opena2a status

Project Security Status
========================
Directory: /home/user/my-agent

Shield:
  Status:       Active
  Protections:  event-log, policy, sessions, integrity
  Mode:         enforce

ConfigGuard:
  Signed files: 4
  Tampered:     0
  Policy:       warn

Identity:
  Local key:    Present (Ed25519)
  Registered:   Yes
  Trust score:  78/100

Tool Detection

The status command automatically detects which OpenA2A tools are installed and their versions. When run with --verbose, it lists detected tools and shows additional details for each status component, including file paths, last-modified timestamps, and configuration values. This is useful for debugging configuration issues or verifying that all tools are correctly installed in a new environment.

Error Handling

The status command always succeeds (exit code 0) even when components are not configured. Unconfigured components are reported as "Not configured" rather than causing failures. This makes it safe to use in scripts and CI pipelines as a diagnostic step. In CI mode, the JSON output includes a configured boolean for each component, which you can use with jq to gate subsequent pipeline steps.

Related Commands

shieldguardidentityreview