socket organization
List organizations associated with the API key used
At the time of writing this should show you the one organization that's associated with the current API token. (This may change in the future)
socket organization --help
$ socket organization --help
Manage Socket organization account details
Usage
$ socket organization <command>
Commands
dependencies Search for any dependency that is being used in your organization
list List organizations associated with the Socket API token
policy Organization policy details
Options
--no-banner Hide the Socket banner
--no-spinner Hide the console spinner
socket organization list
This fetches the name, ID, and plan of each organization. Add --json to also get each organization's slug.
$ socket organization list
✔ Received Socket API response (after requesting organization list).
List of organizations associated with your API token, starting with: abcde
- Name: BearDev, ID: 123, Plan: enterprise
socket organization dependencies
You can use this to find out which dependencies are used in your org and which repository or repositories and which branch may have used them. This is useful in case a bad package was published and you need to quickly figure out where to scrub them from your organization.
$ socket organization dependencies --help
Search for any dependency that is being used in your organization
Usage
socket organization dependencies [options]
API Token Requirements
- Quota: 1 unit
Options
--json Output as JSON
--limit Maximum number of dependencies returned
--markdown Output as Markdown
--offset Page number
Examples
socket organization dependencies
socket organization dependencies --limit 20 --offset 10
The help calls --offset a page number, but it is the number of rows to skip, starting at 0. Use it together with --limit to page through the results.
socket organization policy security
You can pull in the currently configured security policy for your organization. Your API token needs the security-policy:read permission.
socket organization policy license
You can pull in the currently configured license policy for your organization. Your API token needs the license-policy:read permission.
Updated 17 days ago