semgrep-rule-variant-creator

Port a Semgrep rule by analyzing applicability for the target language, translating the rule using AST-informed logic, generating test-first vulnerable and safe examples, and validating that all tests pass.

Yes, Semgrep rule translation applies to polyglot codebases by generating independent rule and test files for each target language with consistent naming, requiring mandatory applicability analysis before porting.

Naïve Semgrep rule translation causes false positives and missed findings because it lacks AST-informed rule translation and test-first generation with required vulnerable and safe examples to guarantee correctness.

Write tests for a translated Semgrep rule using test-first variant creation, generating language-specific test cases with required vulnerable and safe examples, then validating with Semgrep to require all tests pass.

You should skip porting a Semgrep rule when mandatory applicability analysis determines the rule is not applicable to the target language, rather than forcing an adaptation that may produce incorrect detection logic.

Yes, taint analysis rules can be ported to new target languages using AST-informed rule translation, producing independent rule and test files with correctness guarantees validated by passing all Semgrep tests.