@salesforce/cli 2.48.3 → 2.48.5

package/oclif.manifest.json

@@ -4685,9 +4685,9 @@
     "scanner:run": {
       "aliases": [],
       "args": {},
-      "description": "Scans a codebase with a selection of rules. You can scan the codebase with all the rules in the registry, or use parameters to filter the rules based on rulename, category, or ruleset. You can specify the format of the output, such as XML or JUnit. You can print the output to the console (default) or to a file using the --outfile parameter.",
+      "description": "Specify the format of the output, such as XML or JUnit. Print the output to the console (default) or to a file using the --outfile parameter.",
       "examples": [
-        "This example evaluates all rules against somefile.js.\nInvoking code analyzer without specifying any rules causes all rules to be run.\n\t$ <%= config.bin %> <%= command.id %> --format xml --target \"somefile.js\"\n\nThis example evaluates all rules in the Design and Best Practices categories.\nWhen you specify multiple categories or rulesets, the results are combined with a logical OR.\n\t$ <%= config.bin %> <%= command.id %> --format xml --target \"somefile.js\" --\n\nThis example evaluates all rules except those in the Design or Best Practices categories.\nExclude categories by specifying the negation operator and enclosing the values in single quotes.\n\t$ <%= config.bin %> <%= command.id %> --format xml --target \"somefile.js\" --category '!Design,!Best Practices'\n\nWrap globs in quotes. These examples evaluate rules against all .js files in the current directory, except for IgnoreMe.js.\nUnix example:\n\t$ <%= config.bin %> <%= command.id %> --target './**/*.js,!./**/IgnoreMe.js' ...\nWindows example:\n\t$ <%= config.bin %> <%= command.id %> --target \".\\**\\*.js,!.\\**\\IgnoreMe.js\" ...\n\nThis example scans the project contained in '/my-project' if the current working directory is another directory.\nSpecify tsconfig.json if the current working directory does not contain the tsconfig.json that corresponds to the TypeScript files being scanned.\n\t$ <%= config.bin %> <%= command.id %> --target \"/my-project/**/*.ts\" --tsconfig \"/my-project/tsconfig.json\"\n\nThis example evaluates rules against somefile.js, including Jasmine in the environment variables.\nUses --env to override the default ESLint environment variables to add frameworks.\n\t$ <%= config.bin %> <%= command.id %> --target \"somefile.js\" --env '{\"jasmine\": true}'\n\nThis example evaluates rules aginst somefile.js using eslint-lwc and pmd engines.\nUse --engine to include or exclude engines. Any engine listed will be run, regardless of its current 'disabled' attribute.\n\t$ <%= config.bin %> <%= command.id %> --target \"somefile.js\" --engine \"eslint-lwc,pmd\"\n\nThis example executes CPD engine against known file extensions in \"/some/dir\". CPD helps detect blocks of code duplication in selected languages.\nUse --engine to invoke engines that are not enabled by default.\n\t$ <%= config.bin %> <%= command.id %> --target \"/some/dir\" --engine cpd\n\nThis example executes rules defined in pmd_rule_ref.xml against the files in 'src'.\nTo use PMD with your own rule reference file, use --pmdconfig. Note that rule filters are not applied.\n\t$ <%= config.bin %> <%= command.id %> --target \"src\" --pmdconfig \"pmd_rule_ref.xml\"\n\nThis example uses a custom config to scan the files in 'src'.\nTo use ESLint with your own .eslintrc.json file, use --eslintconfig. Make sure that the directory you run the command from has all the NPM dependencies installed.\n\t$ <%= config.bin %> <%= command.id %> --target \"src\" --eslintconfig \"/home/my/setup/.eslintrc.json\"\n\nThis example uses --normalize-severity to output normalized severity and engine-specific severity across all engines. Normalized severity is: 1 (high), 2 (moderate), and 3 (low).\n\t$ <%= config.bin %> <%= command.id %> --target \"/some-project/\" --format csv --normalize-severity\n\nThis example uses --severity-threshold to throw a non-zero exit code when rule violations of normalized severity 2 or greater are found. If any violations with the specified severity (or greater) are found, the exit code equals the severity of the most severe violation.\n\t$ <%= config.bin %> <%= command.id %> --target \"/some-project/\" --severity-threshold 2\n\nThe paths specified for --projectdir must contain all files specified through --target cumulatively.\n\t$ <%= config.bin %> <%= command.id %> --target \"./myproject/main/default/classes/*.cls\" --projectdir \"./myproject/\"\n\t$ <%= config.bin %> <%= command.id %> --target \"./**/*.cls\" --projectdir \"./\"\n\t$ <%= config.bin %> <%= command.id %> --target \"./dir1/file1.cls,./dir2/file2.cls\" --projectdir \"./dir1/,./dir2/\"\n\nThis example fails because the set of files included in --target is larger than that contained in --projectdir:\n\t$ <%= config.bin %> <%= command.id %> --target \"./**/*.cls\" --projectdir \"./myproject/\""
+        "This example evaluates all rules against somefile.js. Invoking code analyzer without specifying any rules causes all rules to be run.\n<%= config.bin %> <%= command.id %> --format xml --target \"somefile.js\"\nThis example evaluates all rules in the Design and Best Practices categories. When you specify multiple categories or rulesets, the results are combined with a logical OR.\n<%= config.bin %> <%= command.id %> --format xml --target \"somefile.js\" --\nThese examples evaluate rules against all .js files in the current directory, except for IgnoreMe.js. Unix example:\n<%= config.bin %> <%= command.id %> --target './**/*.js,!./**/IgnoreMe.js' ...\nWindows example:\n<%= config.bin %> <%= command.id %> --target \".\\**\\*.js,!.\\**\\IgnoreMe.js\" ...\nThis example scans the project contained in '/my-project' if the current working directory is another directory. Specify tsconfig.json if the current working directory does not contain the tsconfig.json that corresponds to the TypeScript files being scanned.\n<%= config.bin %> <%= command.id %> --target \"/my-project/**/*.ts\" --tsconfig \"/my-project/tsconfig.json\"\nThis example evaluates rules against somefile.js, including Jasmine in the environment variables. Uses --env to override the default ESLint environment variables to add frameworks.\n<%= config.bin %> <%= command.id %> --target \"somefile.js\" --env '{\"jasmine\": true}'\nThis example evaluates rules aginst somefile.js using eslint-lwc and pmd engines. Use --engine to include or exclude engines. Any engine listed will be run, regardless of its current 'disabled' attribute.\n<%= config.bin %> <%= command.id %> --target \"somefile.js\" --engine \"eslint-lwc,pmd\"\nThis example executes CPD engine against known file extensions in \"/some/dir\". CPD helps detect blocks of code duplication in selected languages. Use --engine to invoke engines that are not enabled by default.\n<%= config.bin %> <%= command.id %> --target \"/some/dir\" --engine cpd\nThis example executes rules defined in pmd_rule_ref.xml against the files in 'src'. To use PMD with your own rule reference file, use --pmdconfig. Note that rule filters are not applied.\n<%= config.bin %> <%= command.id %> --target \"src\" --pmdconfig \"pmd_rule_ref.xml\"\nThis example uses a custom config to scan the files in 'src'. To use ESLint with your own .eslintrc.json file, use --eslintconfig. Make sure that the directory you run the command from has all the NPM dependencies installed.\n<%= config.bin %> <%= command.id %> --target \"src\" --eslintconfig \"/home/my/setup/.eslintrc.json\"\nThis example uses --normalize-severity to output normalized severity and engine-specific severity across all engines. Normalized severity is: 1 (high), 2 (moderate), and 3 (low).\n<%= config.bin %> <%= command.id %> --target \"/some-project/\" --format csv --normalize-severity\nThis example uses --severity-threshold to throw a non-zero exit code when rule violations of normalized severity 2 or greater are found. If any violations with the specified severity (or greater) are found, the exit code equals the severity of the most severe violation.\n<%= config.bin %> <%= command.id %> --target \"/some-project/\" --severity-threshold 2\nThese examples explain that the paths specified for --projectdir must contain all files specified through --target cumulatively.\n<%= config.bin %> <%= command.id %> --target \"./myproject/main/default/classes/*.cls\" --projectdir \"./myproject/\"\n<%= config.bin %> <%= command.id %> --target \"./**/*.cls\" --projectdir \"./\"\n<%= config.bin %> <%= command.id %> --target \"./dir1/file1.cls,./dir2/file2.cls\" --projectdir \"./dir1/,./dir2/\"\nThis example fails because the set of files included in --target is larger than that contained in --projectdir.\n<%= config.bin %> <%= command.id %> --target \"./**/*.cls\" --projectdir \"./myproject/\""
       ],
       "flags": {
         "json": {
@@ -4698,17 +4698,16 @@
           "type": "boolean"
         },
         "verbose": {
-          "description": "Emit additional command output to stdout.",
           "name": "verbose",
-          "summary": "emit additional command output to stdout",
+          "summary": "Emit additional command output to stdout.",
           "allowNo": false,
           "type": "boolean"
         },
         "category": {
           "char": "c",
-          "description": "One or more categories of rules to run. Specify multiple values as a comma-separated list.",
+          "description": "Specify multiple values as a comma-separated list.",
           "name": "category",
-          "summary": "one or more categories of rules to run",
+          "summary": "One or more categories of rules to run.",
           "delimiter": ",",
           "hasDynamicHelp": false,
           "multiple": true,
@@ -4716,9 +4715,8 @@
         },
         "format": {
           "char": "f",
-          "description": "Specifies the output format for results written directly to the console.",
           "name": "format",
-          "summary": "specify results output format",
+          "summary": "The output format for results written directly to the console.",
           "hasDynamicHelp": false,
           "multiple": false,
           "options": [
@@ -4734,37 +4732,36 @@
         },
         "outfile": {
           "char": "o",
-          "description": "Writes output to a file.",
           "name": "outfile",
-          "summary": "write output to a file",
+          "summary": "File to write output to.",
           "hasDynamicHelp": false,
           "multiple": false,
           "type": "option"
         },
         "severity-threshold": {
           "char": "s",
-          "description": "Throws an error when violations are found with equal or greater severity than the provided value. Values are 1 (high), 2 (moderate), and 3 (low). Exit code is the most severe violation. Using this flag also invokes the --normalize-severity flag.",
+          "description": "Values are 1 (high), 2 (moderate), and 3 (low). Exit code is the most severe violation. Using this flag also invokes the --normalize-severity flag.",
           "exclusive": [
             "json"
           ],
           "name": "severity-threshold",
-          "summary": "throw an error when a violation threshold is reached, the --normalize-severity is invoked, and severity levels are reset to the baseline",
+          "summary": "An error will be thrown when a violation is found with a severity equal to or greater than the specified level.",
           "hasDynamicHelp": false,
           "multiple": false,
           "type": "option"
         },
         "normalize-severity": {
-          "description": "Returns normalized severity 1 (high), 2 (moderate), and 3 (low), and the engine-specific severity. For the html option, the normalized severity is displayed instead of the engine severity.",
+          "description": "For the html option, the normalized severity is displayed instead of the engine severity.",
           "name": "normalize-severity",
-          "summary": "return normalized severity 1 (high), 2 (moderate), and 3 (low), and the engine-specific severity",
+          "summary": "Include normalized severity levels 1 (high), 2 (moderate), and 3 (low) with the results.",
           "allowNo": false,
           "type": "boolean"
         },
         "projectdir": {
           "char": "p",
-          "description": "Provides the relative or absolute root project directories used to set the context for Graph Engine's analysis. Specify multiple values as a comma-separated list. Each project directory must be a path, not a glob. If --projectdir isn’t specified, a default value is calculated. The default value is a directory that contains all the target files.",
+          "description": "Specify multiple values as a comma-separated list. Each project directory must be a path, not a glob. If --projectdir isn’t specified, a default value is calculated. The default value is a directory that contains all the target files.",
           "name": "projectdir",
-          "summary": "root directory of project",
+          "summary": "The relative or absolute root project directories used to set the context for Graph Engine's analysis.",
           "delimiter": ",",
           "hasDynamicHelp": false,
           "multiple": true,
@@ -4775,9 +4772,9 @@
           "deprecated": {
             "message": "The 'ruleset' command parameter is deprecated. Use 'category' instead."
           },
-          "description": "Deprecated. Use category instead. One or more rulesets to run. Specify multiple values as a comma-separated list.",
+          "description": "Use category instead. One or more rulesets to run. Specify multiple values as a comma-separated list.",
           "name": "ruleset",
-          "summary": "[Deprecated] rulesets to run",
+          "summary": "[Deprecated] Rulesets to run.",
           "delimiter": ",",
           "hasDynamicHelp": false,
           "multiple": true,
@@ -4785,9 +4782,9 @@
         },
         "engine": {
           "char": "e",
-          "description": "Specifies one or more engines to run. Submit multiple values as a comma-separated list.",
+          "description": "Submit multiple values as a comma-separated list.",
           "name": "engine",
-          "summary": "specify which engines to run",
+          "summary": "Specify which engines to run.",
           "delimiter": ",",
           "hasDynamicHelp": false,
           "multiple": true,
@@ -4805,60 +4802,49 @@
         },
         "target": {
           "char": "t",
-          "description": "Specifies the source code location. Can use glob patterns. Specify multiple values as a comma-separated list. Default is \".\".",
+          "description": "Specify multiple values as a comma-separated list. Can use glob patterns. Default is \".\".",
           "name": "target",
-          "summary": "source code location",
+          "summary": "Source code location.",
           "delimiter": ",",
           "hasDynamicHelp": false,
           "multiple": true,
           "type": "option"
         },
         "tsconfig": {
-          "description": "The location of the tsconfig.json file used by the eslint-typescript engine. The --tsconfig flag can’t be used with --eslintconfig flag.",
           "name": "tsconfig",
-          "summary": "location of tsconfig.json file",
+          "summary": "Location of tsconfig.json file used by the eslint-typescript engine. The --tsconfig flag can’t be used with --eslintconfig flag.",
           "hasDynamicHelp": false,
           "multiple": false,
           "type": "option"
         },
         "eslintconfig": {
-          "description": "Specifies the location of eslintrc config to customize ESLint engine. The --tsconfig flag can’t be used with --eslintconfig flag.",
           "name": "eslintconfig",
-          "summary": "specify the location of eslintrc config to customize eslint engine",
+          "summary": "Specify the location of eslintrc config to customize eslint engine. The --tsconfig flag can’t be used with --eslintconfig flag.",
           "hasDynamicHelp": false,
           "multiple": false,
           "type": "option"
         },
         "pmdconfig": {
-          "description": "Specifies the location of the PMD rule reference XML file to customize rule selection.",
           "name": "pmdconfig",
-          "summary": "specify location of PMD rule reference XML file to customize rule selection",
+          "summary": "Location of PMD rule reference XML file to customize rule selection.",
           "hasDynamicHelp": false,
           "multiple": false,
           "type": "option"
         },
-        "preview-pmd7": {
-          "description": "Uses PMD version 7.0.0-rc4 instead of 6.55.0 when running PMD and CPD engines.",
-          "name": "preview-pmd7",
-          "summary": "use PMD version 7.0.0-rc4 when running PMD and CPD",
-          "allowNo": false,
-          "type": "boolean"
-        },
         "env": {
           "deprecated": {
             "message": "--env parameter is being deprecated, and will be removed in a future release."
           },
-          "description": "Deprecated. Overrides ESLint's default environmental variables, in JSON-formatted string.",
+          "description": "Overrides ESLint's default environmental variables, in JSON-formatted string.",
           "name": "env",
-          "summary": "[Deprecated] override ESLint's default environment variables, in JSON-formatted string",
+          "summary": "[Deprecated] Override ESLint's default environment variables, in JSON-formatted string.",
           "hasDynamicHelp": false,
           "multiple": false,
           "type": "option"
         },
         "verbose-violations": {
-          "description": "Returns retire-js violation-message details about each vulnerability, including summary, common vulnerabilities and exposures (CVE), and URLs.",
           "name": "verbose-violations",
-          "summary": "return retire-js violation message details",
+          "summary": "Includes Retire-js violation-message details about each vulnerability in the results, including summary, common vulnerabilities and exposures (CVE), and URLs.",
           "allowNo": false,
           "type": "boolean"
         }
@@ -4870,7 +4856,7 @@
       "pluginName": "@salesforce/sfdx-scanner",
       "pluginType": "jit",
       "strict": true,
-      "summary": "scan a codebase with a selection of rules",
+      "summary": "Scan a codebase with all the rules in the registry, or use parameters to filter the rules based on rulename, category, or ruleset.",
       "enableJsonFlag": true,
       "SF_ENV": "SF_ENV",
       "invocation": "scanner run",
@@ -4890,9 +4876,9 @@
     "scanner:rule:add": {
       "aliases": [],
       "args": {},
-      "description": "Adds custom rules to Salesforce Code Analyzer's registry so that you can run them along with the built-in rules. Compile and test custom rules separately before adding them.",
+      "description": "Bundle custom PMD rules in JAR files. Follow PMD conventions, such as defining the custom rules in XML files under a `/category/` directory. Compile and test custom rules separately before adding them. See PMD's documentation for more information on writing rules.",
       "examples": [
-        "Bundle custom PMD rules in JAR files. Follow PMD conventions, such as defining the custom rules in XML files under a `/category/` directory.\nSee PMD's documentation for more information on writing rules.\n\nThis example shows how to specify two JAR files directly.\n\t$ <%= config.bin %> <%= command.id %> --language apex --path \"/Users/me/rules/Jar1.jar,/Users/me/rules/Jar2.jar\"\n\t\tSuccessfully added rules for apex.\n\t\t2 path(s) added:\n\t\t/Users/me/rules/Jar1.jar,/Users/me/rules/Jar2.jar\n\nThis example shows how to specify a directory containing one or more JARs, all of which are added to the registry.\n\t$ <%= config.bin %> <%= command.id %> --language apex --path \"/Users/me/rules\"\n\t\tSuccessfully added rules for apex."
+        "This example shows how to specify two JAR files directly.\n<%= config.bin %> <%= command.id %> --language apex --path \"/Users/me/rules/Jar1.jar,/Users/me/rules/Jar2.jar\"\nThis example shows how to specify a directory containing one or more JARs, all of which are added to the registry.\n<%= config.bin %> <%= command.id %> --language apex --path \"/Users/me/rules\""
       ],
       "flags": {
         "json": {
@@ -4904,20 +4890,19 @@
         },
         "language": {
           "char": "l",
-          "description": "Language that the custom rules are evaluated against.",
           "name": "language",
           "required": true,
-          "summary": "language that the custom rules are evaluated against",
+          "summary": "Language that the custom rules are evaluated against.",
           "hasDynamicHelp": false,
           "multiple": false,
           "type": "option"
         },
         "path": {
           "char": "p",
-          "description": "One or more paths (such as a directory or JAR file) to custom rule definitions. Specify multiple values as a comma-separated list.",
+          "description": "Specify multiple values as a comma-separated list.",
           "name": "path",
           "required": true,
-          "summary": "one or more paths (such as a directory or JAR file) to custom rule definitions",
+          "summary": "One or more paths (such as a directory or JAR file) to custom rule definitions.",
           "delimiter": ",",
           "hasDynamicHelp": false,
           "multiple": true,
@@ -4931,7 +4916,7 @@
       "pluginName": "@salesforce/sfdx-scanner",
       "pluginType": "jit",
       "strict": true,
-      "summary": "add custom rules to Salesforce Code Analyzer's registry",
+      "summary": "Add custom rules to Salesforce Code Analyzer's registry to run them along with the built-in rules.",
       "enableJsonFlag": true,
       "SF_ENV": "SF_ENV",
       "isESM": false,
@@ -4955,9 +4940,8 @@
     "scanner:rule:describe": {
       "aliases": [],
       "args": {},
-      "description": "Provides detailed information about a rule. Information includes the rule's language (such as Apex or Java), the violation it detects, and example code of the violation. The command output also includes the rule's categories and rulesets.",
       "examples": [
-        "$ <%= config.bin %> <%= command.id %> --rulename ExampleRule\n\tname:        AvoidWithStatement\n\tcategories:   Best Practices\n\trulesets:    Controversial Ecmascript\n\tlanguages:   javascript\n\tdescription: Avoid using with - it's bad news\n\tmessage:     Avoid using with - it's bad news"
+        "This example shows how to describe the ApexBadCrypto rule.\n<%= config.bin %> <%= command.id %> --rulename ApexBadCrypto"
       ],
       "flags": {
         "json": {
@@ -4969,25 +4953,16 @@
         },
         "rulename": {
           "char": "n",
-          "description": "The name of the rule.",
           "name": "rulename",
           "required": true,
-          "summary": "the name of the rule",
+          "summary": "The name of the rule.",
           "hasDynamicHelp": false,
           "multiple": false,
           "type": "option"
         },
         "verbose": {
-          "description": "Emit additional command output to stdout.",
           "name": "verbose",
-          "summary": "emit additional command output to stdout",
-          "allowNo": false,
-          "type": "boolean"
-        },
-        "preview-pmd7": {
-          "description": "Uses PMD version 7.0.0-rc4 instead of 6.55.0 to describe PMD and CPD rules.",
-          "name": "preview-pmd7",
-          "summary": "use PMD version 7.0.0-rc4 to describe PMD and CPD rules",
+          "summary": "Emit additional command output to stdout.",
           "allowNo": false,
           "type": "boolean"
         }
@@ -4999,7 +4974,7 @@
       "pluginName": "@salesforce/sfdx-scanner",
       "pluginType": "jit",
       "strict": true,
-      "summary": "provide detailed information about a rule",
+      "summary": "Provide detailed information about a rule that includes the rule's language (such as Apex or Java), the violation it detects, example code of the violation, and the rule's categories and rulesets.",
       "enableJsonFlag": true,
       "SF_ENV": "SF_ENV",
       "isESM": false,
@@ -5023,9 +4998,9 @@
     "scanner:rule:list": {
       "aliases": [],
       "args": {},
-      "description": "Lists all the rules available in the catalog. You can filter the output to view a smaller set of rules. To get more information about a specific rule, use the `scanner rule describe` command.",
+      "description": "Filter the output to view a smaller set of rules. Use the `scanner rule describe` command to get information about a specific rule.",
       "examples": [
-        "This example invokes the command without filter criteria, which returns all rules.\n\t$ <%= config.bin %> <%= command.id %>\n\nThis example returns all rules for Apex OR Javascript. Values supplied to a single filter are handled with a logical OR.\n\t$ <%= config.bin %> <%= command.id %> --language apex,javascript\n\nThis example returns all rules except those in the Design or Best Practices categories. Exclude categories by specifying the negation operator and enclosing the values in single quotes.\n\t$ <%= config.bin %> <%= command.id %> --category '!Design,!Best Practices'\n\nThis example returns all rules that target Apex OR Javascript, AND are members of the Braces OR Security rulesets.\nThe different filters are combined with a logical AND.\n\t$ <%= config.bin %> <%= command.id %> --language apex,javascript --ruleset Braces,Security"
+        "This example invokes the command without filter criteria, which returns all rules.\n<%= config.bin %> <%= command.id %>\nThis example returns all rules for Apex OR Javascript. Values supplied to a single filter are handled with a logical OR.\n<%= config.bin %> <%= command.id %> --language apex,javascript\nThis example returns all rules that target Apex OR Javascript, AND are members of the Braces OR Security rulesets. The different filters are combined with a logical AND.\n<%= config.bin %> <%= command.id %> --language apex,javascript --ruleset Braces,Security"
       ],
       "flags": {
         "json": {
@@ -5036,17 +5011,16 @@
           "type": "boolean"
         },
         "verbose": {
-          "description": "Emit additional command output to stdout.",
           "name": "verbose",
-          "summary": "emit additional command output to stdout",
+          "summary": "Emit additional command output to stdout.",
           "allowNo": false,
           "type": "boolean"
         },
         "category": {
           "char": "c",
-          "description": "Selects rules by category. Enter multiple values as a comma-separated list.",
+          "description": "Specify multiple values as a comma-separated list.",
           "name": "category",
-          "summary": "select rules by category",
+          "summary": "Select rules by category.",
           "delimiter": ",",
           "hasDynamicHelp": false,
           "multiple": true,
@@ -5057,9 +5031,8 @@
           "deprecated": {
             "message": "The 'ruleset' command parameter is deprecated. Use 'category' instead"
           },
-          "description": "Deprecated. Use category instead. Selects rules by ruleset. Enter multiple values as a comma-separated list.",
           "name": "ruleset",
-          "summary": "[Deprecated] select rules by ruleset",
+          "summary": "Deprecated. Use category instead. Select rules by ruleset.",
           "delimiter": ",",
           "hasDynamicHelp": false,
           "multiple": true,
@@ -5067,9 +5040,9 @@
         },
         "language": {
           "char": "l",
-          "description": "Selects rules by language. Enter multiple values as a comma-separated list.",
+          "description": "Specify multiple values as a comma-separated list.",
           "name": "language",
-          "summary": "select rules by language",
+          "summary": "Select rules by language.",
           "delimiter": ",",
           "hasDynamicHelp": false,
           "multiple": true,
@@ -5077,9 +5050,9 @@
         },
         "engine": {
           "char": "e",
-          "description": "Selects rules by engine. Enter multiple engines as a comma-separated list.",
+          "description": "Specify multiple values as a comma-separated list.",
           "name": "engine",
-          "summary": "select rules by engine",
+          "summary": "Select rules by engine.",
           "delimiter": ",",
           "hasDynamicHelp": false,
           "multiple": true,
@@ -5094,13 +5067,6 @@
             "sfge"
           ],
           "type": "option"
-        },
-        "preview-pmd7": {
-          "description": "Uses PMD version 7.0.0-rc4 instead of 6.55.0 to list PMD and CPD rules.",
-          "name": "preview-pmd7",
-          "summary": "use PMD version 7.0.0-rc4 to list PMD and CPD rules",
-          "allowNo": false,
-          "type": "boolean"
         }
       },
       "hasDynamicHelp": false,
@@ -5110,7 +5076,7 @@
       "pluginName": "@salesforce/sfdx-scanner",
       "pluginType": "jit",
       "strict": true,
-      "summary": "list basic information about all rules matching provided criteria",
+      "summary": "List basic information about all rules matching provided criteria.",
       "enableJsonFlag": true,
       "SF_ENV": "SF_ENV",
       "isESM": false,
@@ -5134,9 +5100,9 @@
     "scanner:rule:remove": {
       "aliases": [],
       "args": {},
-      "description": "Removes custom rules from the registry of available rules. Use the `-p|--path` parameter to specify one or more paths to remove. If you don't specify any parameters, the command lists all valid custom paths but doesn't remove any.",
+      "description": "Use the `-p|--path` parameter to specify one or more paths to remove. If you don't specify any parameters, the command lists all valid custom paths but doesn't remove any.",
       "examples": [
-        "This example runs the command without arguments to see a list of registered custom paths.\n\t$ <%= config.bin %> <%= command.id %>\n\nThis example uses the --path parameter to deregister the rules defined in somerules.jar and any JARs/XMLs contained in the rules folder.\n\t$ <%= config.bin %> <%= command.id %> --path \"~/path/to/somerules.jar,~/path/to/folder/containing/rules\"\n\nThis example uses the --force flag to bypass the confirmation prompt, removing all rules defined in somerules.jar.\nBy default, a list of all rules that will be unregistered is displayed, and the action must be confirmed. To bypass that confirmation, use the --force flag.\n\t$ <%= config.bin %> <%= command.id %> --force --path \"~/path/to/somerules.jar\""
+        "This example runs the command without arguments to see a list of registered custom paths.\n<%= config.bin %> <%= command.id %>\nThis example uses the --path parameter to deregister the rules defined in somerules.jar and any JARs/XMLs contained in the rules folder.\n<%= config.bin %> <%= command.id %> --path \"~/path/to/somerules.jar,~/path/to/folder/containing/rules\"\nThis example uses the --force flag to bypass the confirmation prompt, removing all rules defined in somerules.jar. By default, a list of all rules that will be unregistered is displayed, and the action must be confirmed. To bypass that confirmation, use the --force flag.\n<%= config.bin %> <%= command.id %> --force --path \"~/path/to/somerules.jar\""
       ],
       "flags": {
         "json": {
@@ -5147,25 +5113,23 @@
           "type": "boolean"
         },
         "verbose": {
-          "description": "Emit additional command output to stdout.",
           "name": "verbose",
-          "summary": "emit additional command output to stdout",
+          "summary": "Emit additional command output to stdout.",
           "allowNo": false,
           "type": "boolean"
         },
         "force": {
           "char": "f",
-          "description": "Bypasses the confirmation prompt and immediately removes the rules.",
           "name": "force",
-          "summary": "bypass the confirmation prompt and immediately remove the rules",
+          "summary": "Bypass the confirmation prompt and immediately remove the rules.",
           "allowNo": false,
           "type": "boolean"
         },
         "path": {
           "char": "p",
-          "description": "One or more paths to remove. Specify multiple values with a comma-separated list.",
+          "description": "Specify multiple values with a comma-separated list.",
           "name": "path",
-          "summary": "one or more paths to remove",
+          "summary": "One or more paths to remove.",
           "delimiter": ",",
           "hasDynamicHelp": false,
           "multiple": true,
@@ -5179,7 +5143,7 @@
       "pluginName": "@salesforce/sfdx-scanner",
       "pluginType": "jit",
       "strict": true,
-      "summary": "remove custom rules from the registry of available rules",
+      "summary": "Remove custom rules from the registry of available rules.",
       "enableJsonFlag": true,
       "SF_ENV": "SF_ENV",
       "isESM": false,
@@ -5203,9 +5167,9 @@
     "scanner:run:dfa": {
       "aliases": [],
       "args": {},
-      "description": "Scans codebase with all DFA rules by default.\n\tSpecify the format of output and print results directly or as contents of a file that you provide with --outfile flag.",
+      "description": "Specify the format of output and print results directly or as contents of a file that you provide with --outfile flag.",
       "examples": [
-        "The paths specified for --projectdir must contain all files specified through --target cumulatively.\n\t$ <%= config.bin %> <%= command.id %> --target \"./myproject/main/default/classes/*.cls\" --projectdir \"./myproject/\"\n\t$ <%= config.bin %> <%= command.id %> --target \"./**/*.cls\" --projectdir \"./\"\n\t$ <%= config.bin %> <%= command.id %> --target \"./dir1/file1.cls,./dir2/file2.cls\" --projectdir \"./dir1/,./dir2/\"\nThis example fails because the set of files included in --target is larger than that contained in --projectdir:\n\t$ <%= config.bin %> <%= command.id %> --target \"./**/*.cls\" --projectdir \"./myproject/\"\nGlobs must be wrapped in quotes, as in these Windows and Unix examples, which evaluate rules against all .cls files in the current directory and subdirectories except for IgnoreMe.cls:\nUnix example:\n\t$ <%= config.bin %> <%= command.id %> --target \"./**/*.cls,!./**/IgnoreMe.cls\" ...\nWindows example:\n\t$ <%= config.bin %> <%= command.id %> --target \".\\**\\*.cls,!.\\**\\IgnoreMe.cls\" ...\nYou can target individual methods within a file with a suffix hash (#) on the file's path, and with a semi-colon-delimited list of method names. This syntax is incompatible with globs and directories. This example evaluates rules against all methods named Method1 or Method2 in File1.cls, and all methods named Method3 in File2.cls:\n\t$ <%= config.bin %> <%= command.id %> --target \"./File1.cls#Method1;Method2,./File2.cls#Method3\" ...\nUse --normalize-severity to output a normalized severity across all engines, in addition to the engine-specific severity. Normalized severity is 1 (high), 2 (moderate), and 3 (low):\n\t$ <%= config.bin %> <%= command.id %> --target \"./some-project/\" --projectdir \"./some-project/\" --format csv --normalize-severity\nUse --severity-threshold to throw a non-zero exit code when rule violations of a specific normalized severity or greater are found. If there are any rule violations with a severity of 2 or 1, the exit code is equal to the severity of the most severe violation:\n\t$ <%= config.bin %> <%= command.id %> --target \"./some-project/\" --projectdir \"./some-project/\" --severity-threshold 2\nuse --rule-thread-count to allow more (or fewer) entrypoints to be evaluated concurrently:\n\t$ <%= config.bin %> <%= command.id %> --rule-thread-count 6 ...\nUse --rule-thread-timeout to increase or decrease the maximum runtime for a single entrypoint evaluation. This increases the timeout from the 15-minute default to 150 minutes:\n\t$ <%= config.bin %> <%= command.id %> --rule-thread-timeout 9000000 ...\nUse --sfgejvmargs to pass Java Virtual Machine args to override system defaults while executing Salesforce Graph Engine's rules.\nThe example overrides the system's default heap space allocation to 8 GB and decreases chances of encountering OutOfMemory error.\n\t$ <%= config.bin %> <%= command.id %> --sfgejvmargs \"-Xmx8g\" ...\nUse --with-pilot to allow execution of pilot rules:\nThis example allows pilot rules in the \"Performance\" category to execute.\n\t$ <%= config.bin %> <%= command.id %> --category 'Performance' --with-pilot ..."
+        "These examples show how the paths specified for --projectdir must contain all files specified through --target cumulatively.\n<%= config.bin %> <%= command.id %> --target \"./**/*.cls\" --projectdir \"./\"\n<%= config.bin %> <%= command.id %> --target \"./dir1/file1.cls,./dir2/file2.cls\" --projectdir \"./dir1/,./dir2/\"\nThis example fails because the set of files included in --target is larger than that contained in --projectdir.\n<%= config.bin %> <%= command.id %> --target \"./**/*.cls\" --projectdir \"./myproject/\"\nGlobs must be wrapped in quotes, as in these Windows and Unix examples, which evaluate rules against all .cls files in the current directory and subdirectories except for IgnoreMe.cls. Unix example:\n<%= config.bin %> <%= command.id %> --target \"./**/*.cls,!./**/IgnoreMe.cls\" ...\nWindows example:\n<%= config.bin %> <%= command.id %> --target \".\\**\\*.cls,!.\\**\\IgnoreMe.cls\" ...\nYou can target individual methods within a file with a suffix hash (#) on the file's path, and with a semi-colon-delimited list of method names. This syntax is incompatible with globs and directories. This example evaluates rules against all methods named Method1 or Method2 in File1.cls, and all methods named Method3 in File2.cls.\n<%= config.bin %> <%= command.id %> --target \"./File1.cls#Method1;Method2,./File2.cls#Method3\" ...\nUse --normalize-severity to output a normalized severity across all engines, in addition to the engine-specific severity. Normalized severity is 1 (high), 2 (moderate), and 3 (low).\n<%= config.bin %> <%= command.id %> --target \"./some-project/\" --projectdir \"./some-project/\" --format csv --normalize-severity\nUse --severity-threshold to throw a non-zero exit code when rule violations of a specific normalized severity or greater are found. If there are any rule violations with a severity of 2 or 1, the exit code is equal to the severity of the most severe violation.\n<%= config.bin %> <%= command.id %> --target \"./some-project/\" --projectdir \"./some-project/\" --severity-threshold 2\nUse --rule-thread-count to allow more (or fewer) entrypoints to be evaluated concurrently.\n<%= config.bin %> <%= command.id %> --rule-thread-count 6 ...\nUse --rule-thread-timeout to increase or decrease the maximum runtime for a single entrypoint evaluation. This increases the timeout from the 15-minute default to 150 minutes.\n<%= config.bin %> <%= command.id %> --rule-thread-timeout 9000000 ...\nUse --sfgejvmargs to pass Java Virtual Machine args to override system defaults while executing Salesforce Graph Engine's rules. The example overrides the system's default heap space allocation to 8 GB and decreases chances of encountering OutOfMemory error.\n<%= config.bin %> <%= command.id %> --sfgejvmargs \"-Xmx8g\" ...\nUse --with-pilot to allow execution of pilot rules. This example allows pilot rules in the \"Performance\" category to execute.\n<%= config.bin %> <%= command.id %> --category 'Performance' --with-pilot ..."
       ],
       "flags": {
         "json": {
@@ -5216,17 +5180,16 @@
           "type": "boolean"
         },
         "verbose": {
-          "description": "Emit additional command output to stdout.",
           "name": "verbose",
-          "summary": "emit additional command output to stdout",
+          "summary": "Emit additional command output to stdout.",
           "allowNo": false,
           "type": "boolean"
         },
         "category": {
           "char": "c",
-          "description": "One or more categories of rules to run. Specify multiple values as a comma-separated list.",
+          "description": "Specify multiple values as a comma-separated list.",
           "name": "category",
-          "summary": "one or more categories of rules to run",
+          "summary": "One or more categories of rules to run.",
           "delimiter": ",",
           "hasDynamicHelp": false,
           "multiple": true,
@@ -5234,9 +5197,8 @@
         },
         "format": {
           "char": "f",
-          "description": "Specifies the output format for results written directly to the console.",
           "name": "format",
-          "summary": "specify results output format",
+          "summary": "The output format for results written directly to the console.",
           "hasDynamicHelp": false,
           "multiple": false,
           "options": [
@@ -5252,98 +5214,94 @@
         },
         "outfile": {
           "char": "o",
-          "description": "Writes output to a file.",
           "name": "outfile",
-          "summary": "write output to a file",
+          "summary": "File to write output to.",
           "hasDynamicHelp": false,
           "multiple": false,
           "type": "option"
         },
         "severity-threshold": {
           "char": "s",
-          "description": "Throws an error when violations are found with equal or greater severity than the provided value. Values are 1 (high), 2 (moderate), and 3 (low). Exit code is the most severe violation. Using this flag also invokes the --normalize-severity flag.",
+          "description": "Values are 1 (high), 2 (moderate), and 3 (low). Exit code is the most severe violation. Using this flag also invokes the --normalize-severity flag.",
           "exclusive": [
             "json"
           ],
           "name": "severity-threshold",
-          "summary": "throw an error when a violation threshold is reached, the --normalize-severity is invoked, and severity levels are reset to the baseline",
+          "summary": "An error will be thrown when a violation is found with a severity equal to or greater than the specified level.",
           "hasDynamicHelp": false,
           "multiple": false,
           "type": "option"
         },
         "normalize-severity": {
-          "description": "Returns normalized severity 1 (high), 2 (moderate), and 3 (low), and the engine-specific severity. For the html option, the normalized severity is displayed instead of the engine severity.",
+          "description": "For the html option, the normalized severity is displayed instead of the engine severity.",
           "name": "normalize-severity",
-          "summary": "return normalized severity 1 (high), 2 (moderate), and 3 (low), and the engine-specific severity",
+          "summary": "Include normalized severity levels 1 (high), 2 (moderate), and 3 (low) with the results.",
           "allowNo": false,
           "type": "boolean"
         },
         "projectdir": {
           "char": "p",
-          "description": "Provides the relative or absolute root project directories used to set the context for Graph Engine's analysis. Specify multiple values as a comma-separated list. Each project directory must be a path, not a glob. If --projectdir isn’t specified, a default value is calculated. The default value is a directory that contains all the target files.",
+          "description": "Specify multiple values as a comma-separated list. Each project directory must be a path, not a glob. If --projectdir isn’t specified, a default value is calculated. The default value is a directory that contains all the target files.",
           "name": "projectdir",
-          "summary": "root directory of project",
+          "summary": "The relative or absolute root project directories used to set the context for Graph Engine's analysis.",
           "delimiter": ",",
           "hasDynamicHelp": false,
           "multiple": true,
           "type": "option"
         },
         "with-pilot": {
-          "description": "Allows pilot rules to execute.",
           "name": "with-pilot",
-          "summary": "allow pilot rules to execute",
+          "summary": "Allow pilot rules to execute.",
           "allowNo": false,
           "type": "boolean"
         },
         "target": {
           "char": "t",
-          "description": "Specifies the source code location. Use glob patterns or specify individual methods with #-syntax. Multiple values are specified as a comma-separated list. Default is \".\".",
+          "description": "Use glob patterns or specify individual methods with #-syntax. Multiple values are specified as a comma-separated list. Default is \".\".",
           "name": "target",
-          "summary": "source code location",
+          "summary": "Source code location.",
           "delimiter": ",",
           "hasDynamicHelp": false,
           "multiple": true,
           "type": "option"
         },
         "rule-thread-count": {
-          "description": "Specifies the number of rule-evaluation threads or how many entry points can be evaluated concurrently. Inherits its value from the SFGE_RULE_THREAD_COUNT environment variable, if set. The default is 4.",
           "env": "SFGE_RULE_THREAD_COUNT",
           "name": "rule-thread-count",
-          "summary": "specify number of threads that evaluate DFA rules. Alternatively, set value using environment variable `SFGE_RULE_THREAD_COUNT`. Default is 4",
+          "summary": "Number of DFA rule-evaluation threads or how many entry points can be evaluated concurrently. Inherits its value from the SFGE_RULE_THREAD_COUNT environment variable, if set.",
           "hasDynamicHelp": false,
           "multiple": false,
           "type": "option"
         },
         "rule-thread-timeout": {
-          "description": "Specifies the time limit for evaluating a single entry point in milliseconds. Inherits its value from the SFGE_RULE_THREAD_TIMEOUT environment variable, if set. The default is 900,000 ms or 15 minutes.",
           "env": "SFGE_RULE_THREAD_TIMEOUT",
           "name": "rule-thread-timeout",
-          "summary": "specify timeout for individual rule threads in milliseconds. Alternatively, set the timeout value using environment variable `SFGE_RULE_THREAD_TIMEOUT`. Default: 900000 ms",
+          "summary": "Time limit, in milliseconds, for evaluating a single entry point. Inherits its value from the \"SFGE_RULE_THREAD_TIMEOUT\" environment variable, if set.",
           "hasDynamicHelp": false,
           "multiple": false,
           "type": "option"
         },
         "rule-disable-warning-violation": {
-          "description": "Disables warning violations, such as those on StripInaccessible READ access, to get only high-severity violations (default: false). Inherits value from SFGE_RULE_DISABLE_WARNING_VIOLATION env-var if set.",
+          "description": "Examples of warning violations include those on StripInaccessible READ access, to get only high-severity violations.",
           "name": "rule-disable-warning-violation",
-          "summary": "disable warning violations from Salesforce Graph Engine. Alternatively, set value using environment variable `SFGE_RULE_DISABLE_WARNING_VIOLATION`",
+          "summary": "Disable warning violations from Salesforce Graph Engine. Inherits value from SFGE_RULE_DISABLE_WARNING_VIOLATION env-var, if set.",
           "allowNo": false,
           "type": "boolean"
         },
         "sfgejvmargs": {
-          "description": "Specifies Java Virtual Machine arguments to override system defaults while executing Salesforce Graph Engine. For multiple arguments, add them to the same string separated by space.",
+          "description": "Separate multiple arguments by a space.",
           "env": "SFGE_JVM_ARGS",
           "name": "sfgejvmargs",
-          "summary": "specify Java Virtual Machine (JVM) arguments to optimize Salesforce Graph Engine execution to your system (optional)",
+          "summary": "Java Virtual Machine (JVM) arguments to override system defaults while executing Salesforce Graph Engine.",
           "hasDynamicHelp": false,
           "multiple": false,
           "type": "option"
         },
         "pathexplimit": {
-          "description": "Specifies a path expansion upper boundary to limit the complexity of code Graph Engine analyzes before failing fast. Set the value to -1 to remove any upper boundary. --pathexplimit inherits value from SFGE_PATH_EXPANSION_LIMIT env-var, if set. Its default value is derived from JVM heap space allocation.",
+          "description": "Set the value to -1 to remove any upper boundary. Its default value is derived from JVM heap space allocation.",
           "env": "SFGE_PATH_EXPANSION_LIMIT",
           "name": "pathexplimit",
-          "summary": "specify a path expansion  upper boundary to limit the complexity of code that Graph Engine analyzes. Alternatively, set the value using environment variable `SFGE_PATH_EXPANSION_LIMIT`",
+          "summary": "Path expansion  upper boundary to limit the complexity of code that Graph Engine analyzes before failing test. Inherits it value from the \"SFGE_PATH_EXPANSION_LIMIT\", if set.",
           "hasDynamicHelp": false,
           "multiple": false,
           "type": "option"
@@ -5356,7 +5314,7 @@
       "pluginName": "@salesforce/sfdx-scanner",
       "pluginType": "jit",
       "strict": true,
-      "summary": "scan codebase with all DFA rules",
+      "summary": "Scan codebase with all DFA rules by default.",
       "enableJsonFlag": true,
       "SF_ENV": "SF_ENV",
       "invocation": "scanner run dfa",
@@ -5379,5 +5337,5 @@
       ]
     }
   },
-  "version": "2.48.3"
+  "version": "2.48.5"
 }