remove-guardian-developer-semgrep-rule

From README

Remove a custom Semgrep rule Custom rules are plain files in two directories, both read on every scan: /.semgrep/guardian-rules/ — user scope, this developer everywhere /.semgrep/guardian-rules/ — repo scope, everyone who clones the repository There is no removal tool, because there is nothing to undo in a service: taking a rule off disk is the whole of it. What matters is removing the right one, and knowing who else loses it. Step 1 — List what is there Call listdevelopersemgreprules. It reports both directories, every rule file with its scope and path, whether the rules are being sent, and the deployment's limit. A file holds one rule or several, so check what a file carries before removing it: the count drops by every rule in it. If it refuses because the feature is off for the deployment, the rules on disk are still just files — nothing is being sent, so removal is still fine. List the two directories yourself and carry on.