Live-org verification
Run these steps once after install, and again when you add a new org alias, to confirm vulkro-sf can read the org.
sf --version
sf org login web --alias my-prod
sf org list
vulkro-sf org status --target-org my-prod
If org status prints the org's identity (id, instance, edition, sandbox or production), the connection works.
Run a first audit
vulkro-sf org perms --target-org my-prod
vulkro-sf org packages --target-org my-prod
org perms flags over-privileged profiles and permission sets. org packages lists installed packages and flags unverified ones. Exit code 1 means findings were reported, which is normal on a real org; 0 means none; 2 means an error.
Every read goes through your sf login and only reads: nothing in the org changes. To see the exact calls, run with -v or check the sf CLI's own logs. See Live-org setup for what is read.
Troubleshooting
| Symptom | Cause | Fix |
|---|---|---|
sf: command not found | Salesforce CLI not installed | npm install -g @salesforce/cli, then retry. |
No authorization found for org my-prod | Alias not logged in | sf org login web --alias my-prod. |
Session expired or invalid | The stored token lapsed | Run sf org login web --alias my-prod again. |
INSUFFICIENT_ACCESS, or a read reported as unavailable | The user lacks Setup read access | Use a user with View Setup and Configuration (and View Event Log Files for event checks). |
org perms reports nothing | No over-privilege found | A clean result. Exit code 0. |
license_required | No active trial or Pro on this machine | vulkro-sf login. See Licensing. |
See also: Live-org setup, The sf CLI handoff