vulkro-sf org trust-status
Cross-references the org's instance against a bundled snapshot of
recent trust.salesforce.com incidents.
Reads the org's instance name and matches it against a curated snapshot baked into the binary, so an incident affecting your pod shows up alongside the rest of the live-org audit instead of requiring a separate manual check.
Synopsis
vulkro-sf org trust-status --target-org <alias> [flags]
Flags
| Flag | Type | Default | Description |
|---|---|---|---|
--target-org, -o <alias> | string | (required) | Target org alias or username, as known to sf org login. |
--format <fmt> | table | json | table | Output format. |
--verbose, -v | flag | off | Bump stderr log verbosity. -v enables debug-level tracing for the vulkro + vulkro_sf targets; -vv enables trace. Honoured only when RUST_LOG is unset (an explicit RUST_LOG always wins). |
What gets read
SELECT InstanceName FROM Organization. That single field is the whole
org-side read.
What gets reported
| Rule | Severity | What fires |
|---|---|---|
SF-TRUST-001 | High | The org runs on an instance affected by an unresolved Major or Service Disruption incident. Signal org-trust-incident-major-active. |
SF-TRUST-002 | Medium | The org runs on an instance affected by a Minor incident published in the last 7 days. Signal org-trust-incident-minor-recent. |
SF-TRUST-003 | Low | The org runs on an instance that had a Resolved incident in the last 30 days. Informational. Signal org-trust-incident-resolved-recent. |
Examples
vulkro-sf org trust-status --target-org my-prod
vulkro-sf org trust-status -o my-prod --format json > trust.json
Air-gapped operation and the bundle
The command never contacts trust.salesforce.com and fetches no
incident data at run time: it matches against a bundle that ships inside
the binary. Set VULKRO_OFFLINE=1 for a guaranteed zero-egress run.
The bundle is point-in-time. Because the upstream incidents.rss feed
requires manual curation, the current version carries representative
placeholder incident IDs. Air-gapped operators can sideload a vetted
bundle with
VULKRO_SF_INTEL_TRUST_BUNDLE_OVERRIDE=/path/to/bundle.json.gz.
Exit codes
0- no findings.1- findings reported.2- error.
Scope and honesty
The org is read locally through your own authenticated sf CLI login;
nothing is sent anywhere.
Be clear-eyed about what this command is: a lookup of your instance
name against a snapshot that was current when the binary was built. It
is a convenience pointer, not a live status feed.
trust.salesforce.com remains the authoritative source, and every
finding is something to follow up there. A quiet run means the bundled
snapshot has no matching incident for your instance, which is not
the same as "your instance is healthy right now".
Where to go next
- vulkro-sf org status - the org identity this command reads its instance from.
- vulkro-sf org platform-limits - the org-side availability signal.