{"meta":{"title":"resolve extensions","intro":"[Experimental] [Deep plumbing] Determine accessible extensions. This\nincludes machine learning models and data extensions.","product":"Security and code quality","breadcrumbs":[{"href":"/en/code-security","title":"Security and code quality"},{"href":"/en/code-security/reference","title":"Reference"},{"href":"/en/code-security/reference/code-scanning","title":"Code scanning"},{"href":"/en/code-security/reference/code-scanning/codeql","title":"CodeQL"},{"href":"/en/code-security/reference/code-scanning/codeql/codeql-cli-manual","title":"CodeQL CLI manual"},{"href":"/en/code-security/reference/code-scanning/codeql/codeql-cli-manual/resolve-extensions","title":"resolve extensions"}],"documentType":"article"},"body":"# resolve extensions\n\n[Experimental] [Deep plumbing] Determine accessible extensions. This\nincludes machine learning models and data extensions.\n\n> [!NOTE]\n> This content describes the most recent release of the CodeQL CLI. For more information about this release, see https://github.com/github/codeql-cli-binaries/releases.\n>\n> To see details of the options available for this command in an earlier release, run the command with the <span style=\"white-space: nowrap;\">`--help`</span> option in your terminal.\n\n## Synopsis\n\n```shell copy\ncodeql resolve extensions <options>... -- <query|dir|suite|pack>...\n```\n\n## Description\n\n\\[Deep plumbing] Determine accessible data extensions.\n\nThis plumbing command resolves the set of data extensions that are\navailable to the query specifiers passed in as command line arguments.\n\n## Options\n\n### Primary Options\n\n#### `<query|dir|suite|pack>...`\n\n\\[Mandatory] Queries to execute. Each argument is in the form\n`scope/name@range:path` where:\n\n* `scope/name` is the qualified name of a CodeQL pack.\n* `range` is a semver range.\n* `path` is a file system path.\n\nIf a `scope/name` is specified, the `range` and `path` are optional. A\nmissing `range` implies the latest version of the specified pack. A\nmissing `path` implies the default query suite of the specified pack.\n\nThe `path` can be one of a `*.ql` query file, a directory containing one\nor more queries, or a `.qls` query suite file. If there is no pack name\nspecified, then a `path` must be provided, and will be interpreted\nrelative to the current working directory of the current process.\n\nTo specify a `path` that contains a literal `@` or `:`, use `path:` as a\nprefix to the argument, like this: `path:directory/with:and@/chars`.\n\nIf a `scope/name` and `path` are specified, then the `path` cannot be\nabsolute. It is considered relative to the root of the CodeQL pack.\n\n#### `--search-path=<dir>[:<dir>...]`\n\nA list of directories under which QL packs may be found. Each directory\ncan either be a QL pack (or bundle of packs containing a\n`.codeqlmanifest.json` file at the root) or the immediate parent of one\nor more such directories.\n\nIf the path contains more than one directory, their order defines\nprecedence between them: when a pack name that must be resolved is\nmatched in more than one of the directory trees, the one given first\nwins.\n\nPointing this at a checkout of the open-source CodeQL repository ought\nto work when querying one of the languages that live there.\n\nIf you have checked out the CodeQL repository as a sibling of the\nunpacked CodeQL toolchain, you don't need to give this option; such\nsibling directories will always be searched for QL packs that cannot be\nfound otherwise. (If this default does not work, it is strongly\nrecommended to set up `--search-path` once and for all in a per-user\nconfiguration file).\n\n(Note: On Windows the path separator is `;`).\n\n#### `--additional-packs=<dir>[:<dir>...]`\n\nIf this list of directories is given, they will be searched for packs\nbefore the ones in `--search-path`. The order between these doesn't\nmatter; it is an error if a pack name is found in two different places\nthrough this list.\n\nThis is useful if you're temporarily developing a new version of a pack\nthat also appears in the default path. On the other hand, it is _not\nrecommended_ to override this option in a config file; some internal\nactions will add this option on the fly, overriding any configured\nvalue.\n\n(Note: On Windows the path separator is `;`).\n\n#### `--model-packs=<`<name@range>>...\n\nA list of CodeQL pack names, each with an optional version range, to be\nused as model packs to customize the queries that are about to be\nevaluated.\n\n#### `--threat-model=<name>...`\n\nA list of threat models to enable or disable.\n\nThe argument is the name of a threat model, optionally preceded by a\n'!'. If no '!' is present, the named threat model and all of its\ndescendants are enabled. If a '!' is present, the named threat model\nand all of its descendants are disabled.\n\nThe 'default' threat model is enabled by default, but can be disabled\nby specifying '--threat-model !default'.\n\nThe 'all' threat model can be used to enable or disable all threat\nmodels.\n\nThe --threat-model options are processed in order. For example,\n'--threat-model local --threat-model !environment' enables all of\nthe threat models in the 'local' group except for the 'environment'\nthreat model.\n\nThis option only has an effect for languages that support threat models.\n\nAvailable since `v2.15.3`.\n\n### Options for configuring the CodeQL package manager\n\n#### `--registries-auth-stdin`\n\nAuthenticate to GitHub Enterprise Server Container registries by passing\na comma-separated list of \\<registry\\_url>=\\<token> pairs.\n\nFor example, you can pass\n`https://containers.GHEHOSTNAME1/v2/=TOKEN1,https://containers.GHEHOSTNAME2/v2/=TOKEN2`\nto authenticate to two GitHub Enterprise Server instances.\n\nThis overrides the CODEQL\\_REGISTRIES\\_AUTH and GITHUB\\_TOKEN environment\nvariables. If you only need to authenticate to the github.com Container\nregistry, you can instead authenticate using the simpler\n`--github-auth-stdin` option.\n\n#### `--github-auth-stdin`\n\nAuthenticate to the github.com Container registry by passing a\ngithub.com GitHub Apps token or personal access token via standard\ninput.\n\nTo authenticate to GitHub Enterprise Server Container registries, pass\n`--registries-auth-stdin` or use the CODEQL\\_REGISTRIES\\_AUTH environment\nvariable.\n\nThis overrides the GITHUB\\_TOKEN environment variable.\n\n### Common options\n\n#### `-h, --help`\n\nShow this help text.\n\n#### `-J=<opt>`\n\n\\[Advanced] Give option to the JVM running the command.\n\n(Beware that options containing spaces will not be handled correctly.)\n\n#### `-v, --verbose`\n\nIncrementally increase the number of progress messages printed.\n\n#### `-q, --quiet`\n\nIncrementally decrease the number of progress messages printed.\n\n#### `--verbosity=<level>`\n\n\\[Advanced] Explicitly set the verbosity level to one of errors,\nwarnings, progress, progress+, progress++, progress+++. Overrides `-v`\nand `-q`.\n\n#### `--logdir=<dir>`\n\n\\[Advanced] Write detailed logs to one or more files in the given\ndirectory, with generated names that include timestamps and the name of\nthe running subcommand.\n\n(To write a log file with a name you have full control over, instead\ngive `--log-to-stderr` and redirect stderr as desired.)\n\n#### `--common-caches=<dir>`\n\n\\[Advanced] Controls the location of cached data on disk that will\npersist between several runs of the CLI, such as downloaded QL packs and\ncompiled query plans. If not set explicitly, this defaults to a\ndirectory named `.codeql` in the user's home directory; it will be\ncreated if it doesn't already exist.\n\nAvailable since `v2.15.2`."}