Manage Inth resources from the CLI
Use inth project for consent projects, inth code-audit for repository scans, and inth inbox for findings. Resource writes take effect immediately. Use a saved sign-in or an API key accepted by the command, and check inth <command> --help for required scopes and flags.
Which command manages each resource?
| Command | Operation |
|---|---|
org list, org get <id>, org create | List, read, or create organizations |
region list | List project region IDs |
project list, project get <id> | Read projects, including consent settings |
project create --name <name> --region <id> | Create a project |
project update <id>, project delete <id> | Update or delete a project |
member list, member update <id> --role <role> | Read members or change a role |
member remove <id> | Remove a member |
invitation list, invitation create --email <email> --role <role> | Read pending invitations or send an invitation |
invitation cancel <id> | Cancel a pending invitation |
api-key list, api-key create --name <name> | List or create organization API keys |
api-key roll <id>, api-key delete <id> | Rotate or revoke a key |
billing | Read the organization's plan and credit balance |
code-audit repositories | List connected repositories |
code-audit scans | List scans, optionally with --repository and --status |
code-audit start --repository <id> | Start a scan of the repository's production branch |
code-audit request <preparation-id> --repository <id> | Check a delayed scan request |
code-audit get <id>, code-audit issues <id> | Read a scan or its report |
code-audit unlock <id> | Spend credits to unlock a report |
inbox list, inbox get <id> | Read findings, optionally filtering the list with --status |
inbox update <id> --status <status> --item-version <version> | Change a finding's status |
inbox github-issue <id> | Create a GitHub issue for a finding |
How do I list and configure consent projects?
List commands return one page. --limit defaults to 50 and accepts 1 through 100. Pass the returned cursor unchanged to --cursor for the next page.
Replace the example IDs with IDs returned by the API. Project writes accept --branding inth|c15t|none and a JSON array for --trusted-origins. Use --data '<JSON object>' instead of individual body options for nested fields or explicit null values.
How do I start a Code Audit scan?
Run inth code-audit start --repository <id> with an ID returned by inth code-audit repositories. Supply a stable --request-id when a start may need a manual retry.
A scan start can return starting with a preparationId and repositoryId. Check those IDs with code-audit request until the state is started or failed. Each invocation checks once. Reuse the same --request-id when retrying a start.
How do I update an Inbox finding?
Run inth inbox get <id> to read the finding, then pass the returned version to inth inbox update using --item-version.
Inbox updates require the version from the latest read. Supported statuses are open, accepted, dismissed, and resolved. After a version conflict, read the item again before updating it.
Which commands send messages, expose secrets, or spend credits?
Writes run without confirmation prompts. Invitations send email, key rotation replaces the old key, report unlocks spend credits and require an owner, and inbox github-issue creates a GitHub issue. Key creation and rotation print the new secret once; save it before closing the terminal. An unresolved GitHub issue send can return 409 and require server reconciliation before another attempt.