|
10 | 10 | description: "Semgrep Editor is a powerful tool within Semgrep AppSec Platform to write rules and quickly apply these rules across an organization to enforce coding standards across an organization." |
11 | 11 | --- |
12 | 12 |
|
13 | | -import EnableTurboMode from "/src/components/procedure/_enable-turbo-mode.md" |
14 | 13 | import DeleteCustomRule from "/src/components/procedure/_delete-custom-rule.mdx" |
15 | 14 | import InstallPrivateGitHubApp from "/src/components/procedure/_install-private-github-app.mdx" |
16 | 15 | import ForkExistingRule from '/src/components/reference/_fork_existing_rule.md' |
@@ -142,7 +141,7 @@ Advanced mode is a YAML editor that allows you to write rules using [Semgrep syn |
142 | 141 | :::info Rules syntax |
143 | 142 | Refer to [Rule syntax](/writing-rules/rule-syntax) for all possible fields and values to create a rule. |
144 | 143 |
|
145 | | -To quickly learn Semgrep patterns and syntax, explore the Editor’s library of rules from the **public [Rule Registry](https://semgrep.dev/explore)**. Rules from the Registry can detect OWASP vulnerabilities, best practice violations, and security issues for a wide variety of languages and frameworks. Semgrep Editor enables you to **adapt these rules** for your own organization’s use by [forking](#write-a-new-rule-by-forking-an-existing-rule) them. |
| 144 | +To quickly learn Semgrep patterns and syntax, explore the Editor’s library of rules from the **public [Rule Registry](https://semgrep.dev/explore)**. Rules from the Registry can detect OWASP vulnerabilities, best practice violations, and security issues for a wide variety of languages and frameworks. Semgrep Editor enables you to **adapt these rules** for your own organization's use by [forking](#write-a-new-rule-by-forking-an-existing-rule) them. |
146 | 145 | ::: |
147 | 146 |
|
148 | 147 | To write a rule in advanced mode: |
@@ -179,9 +178,7 @@ In addition to testing for matches, you can test that your rule doesn't match wh |
179 | 178 |
|
180 | 179 | Once you've written a rule and created comment annotations, you can run your rule against your comment annotations by clicking **Run**. You can also press <kbd>Ctrl</kbd>+<kbd>Enter</kbd> (<kbd>⌘</kbd>+<kbd>Enter</kbd> on Mac). |
181 | 180 |
|
182 | | -### Turbo mode (beta) |
183 | 181 |
|
184 | | -<EnableTurboMode /> |
185 | 182 |
|
186 | 183 | ## Code search (beta) |
187 | 184 |
|
@@ -227,7 +224,7 @@ Upon saving, a rule’s visibility is **private** by default. A private rule is |
227 | 224 |
|
228 | 225 | Some older rules in Semgrep AppSec Platform may be **unlisted** rather than private. These rules are marked with an icon without a lock, and can be shared with anyone, including those who cannot access Semgrep AppSec Platform. |
229 | 226 |
|
230 | | -To change an unlisted rule's visibility to private for increased security, click **Share > Private > Confirm**. |
| 227 | +To change an unlisted rule’s visibility to private for increased security, click **Share > Private > Confirm**. |
231 | 228 |
|
232 | 229 | ## Rename a rule |
233 | 230 |
|
|
0 commit comments