Skip to main content

vulkro-sf org status

Confirms the live-org connector can reach the named org via your sf CLI login and prints the org's identity. Run this before any other vulkro-sf org subcommand: if connectivity is healthy, every other org subcommand will reach the same org with the same authentication.

The output names the edition, the my-domain, the namespace, and the license count so you can tell at a glance whether you're pointed at a sandbox, a Developer org, or a production org. This is the fastest way to catch the "I thought I was logged into staging" mistake before a report is shared.

Synopsis​

vulkro-sf org status --target-org <alias> [flags]

Flags​

FlagTypeDefaultDescription
--target-org <alias>string(required)The sf CLI org alias to inspect.
--format <fmt>enumtextOutput format: text (a labeled summary on the terminal) or json (machine-readable, e.g. for embedding in a CI annotation).

What gets reported​

  • Org ID - the 15- or 18-character organization identifier.
  • Instance URL - the My Domain URL (e.g. https://acme.my.salesforce.com).
  • My Domain - the configured my-domain value, or a note that the org is still on the legacy login.salesforce.com shape.
  • Namespace - the managed-package namespace, or (none) for orgs that haven't installed a namespaced package.
  • Edition - Developer, Professional, Enterprise, Unlimited, Performance, Essentials, etc.
  • License count - total user licenses purchased on the org.
  • Sandbox flag - whether this org is a sandbox (with the parent production Org ID, if available) or a production org.

Examples​

# Confirm connectivity before running a deeper scan.
vulkro-sf org status --target-org my-prod

# JSON for embedding the org identity in a CI annotation.
vulkro-sf org status --target-org my-prod --format json

Exit codes​

  • 0 - org connectivity succeeded, identity printed.
  • 1 - reserved (this subcommand does not produce findings).
  • 2 - error: sf CLI not on PATH, alias not authenticated, network failure, or the org rejected the metadata API call. The error message names the cause and the next step.

Privacy​

org status reads the OrganizationId, the LimitsInfo envelope, and the getUserInfo response from the sf CLI. No record-data SOQL is issued: no Account, no Opportunity, no Lead, no Contact, no custom sObject row is fetched. The OAuth token stays in the sf CLI credential store on your laptop. The full privacy posture is documented at Install: Privacy.

Where to go next​