{"full_name":"semgrep/semgrep","owner":"semgrep","name":"semgrep","shard":"1","url":"https://github.com/semgrep/semgrep","description":"Lightweight static analysis for many languages. Find bug variants with patterns that look like source code.","homepage":"https://semgrep.dev","topics":["static-analysis","static-code-analysis","java","go","sast","semgrep","r2c","c","python","ruby","javascript","typescript","production"],"tag_pages":["c","go","java","javascript","production","python","ruby","static-analysis","static-code-analysis","typescript"],"language":"C","license":"LGPL-2.1","avatar":"https://avatars.githubusercontent.com/u/29760937?v=4","created_at":"2019-12-13T09:29:54Z","pushed_at":"2026-11-13T00:03:04Z","metrics":{"stars":17694,"forks":1181,"watchers":118,"issues":3352,"prs":8623,"releases":352,"issues_open":912,"issues_closed":2440,"prs_open":88,"prs_closed":1491,"prs_merged":7044,"discussions":2},"growth":{"day":{"stars":7,"forks":2,"base_day":"2026-11-15"}},"history":{"dates":["2026-11-10","2026-11-11","2026-11-12","2026-11-13","2026-11-14","2026-11-15","2026-11-16"],"stars":[17586,17605,17617,17623,17653,17687,17694],"forks":[1163,1164,1165,1167,1171,1179,1181],"watchers":[null,117,117,117,118,118,118],"issues_open":[null,911,911,911,912,912,912],"prs_open":[null,82,84,84,86,88,88]},"boards":{},"same_owner":[],"issues":[{"number":6835,"title":"Include/exclude patterns matching on start/end","comments":26,"created_at":"2023-01-13T15:54:27Z"},{"number":1301,"title":"[Ruby] Typed metavariable handling new, literal arrays","comments":26,"created_at":"2020-07-17T00:28:56Z"},{"number":5665,"title":"Cannot correctly identify hardcoded secrets in YAML files due to intolerance to special characters.","comments":23,"created_at":"2022-06-30T12:21:08Z"},{"number":2991,"title":"yaml parsing: End_of_file exception on Windows","comments":22,"created_at":"2021-04-22T22:00:53Z"},{"number":3304,"title":"Provide better contextual display for patterns with large elisions","comments":18,"created_at":"2021-06-08T10:38:10Z"},{"number":8074,"title":"Group/filter findings in different categories","comments":17,"created_at":"2023-06-16T18:53:02Z"},{"number":4620,"title":"Semgrep tries to pull registry when `--validate` is on","comments":17,"created_at":"2022-02-04T04:17:34Z"},{"number":2663,"title":"semgrep timeout error \"python.lang.maintainability.useless-literal.useless-literal-dict\" on big dictionnaries","comments":17,"created_at":"2021-02-27T11:24:04Z"}],"discussions":[{"number":7155,"title":"Announcing Semgrep Code: SAST designed and built for engineers","comments":0,"category":"Announcements","created_at":"2023-02-14T18:24:04Z"},{"number":6654,"title":"Releasing Semgrep 1.0","comments":0,"category":"Announcements","created_at":"2022-12-02T22:50:27Z"}],"latest_release":{"name":"Release v1.185.0","tag":"v1.185.0","published_at":"2026-11-10T09:32:54Z","body":"## [1.185.0](https://github.com/semgrep/semgrep/releases/tag/v1.185.0) - 2026-11-10\n\n### ### Added\n\n- PHP: Improved virtual call resolution for basic trait composition. (CODE-9176)\n- Supply Chain: a `requirements.txt` dependency declared as a version range (`litellm>=1.10`) or with no version (`flask`) now produces a finding for every advisory whose affected versions overlap the declared range, in both the Python and native resolvers. Such a finding has no single installed version to confirm, so it needs review. A range line next to a pinned copy of the same package produces no finding of its own, since the pinned copy names the installed version. (SC-4243)\n- Secrets: emit structured, privacy-safe telemetry for custom validator HTTP requests (hostname, port, status, latency, rule/scan correlation) (SMS-3122)\n- Set `SEMGREP_LOG_JSON_FILE` to emit structured execution events with scan metadata alongside existing text output. (SMS-3670)\n\n### ### Changed\n\n- Scans are slightly faster. The dataflow analyses build the name of each variable with a plain string join, and no longer with `Printf` and `Format`. On 6 open-source repos, the scan time was a median of 3% lower, with identical findings. (dataflow-variable-keys)\n- The `semgrep/semgrep` Docker image no longer includes the OpenSSH server (`sshd`) or `sftp-server`. It now installs only the OpenSSH client (`ssh`, `scp`, `ssh-keyscan`, `ssh-agent`, `ssh-add` and `ssh-keygen`), which is all git needs to fetch over SSH. Container scanners will no longer report sshd-only CVEs against the image. (docker-ssh-client-only)\n- go grammar update (v0.25.0):\n\n  - Go source parsing now supports generic type aliases, preserving type parameters, constraints, and alias semantics. Existing alias patterns can match these declarations; spelling generic parameter lists in rule patterns remains unsupported.\n  - Go correctly parses unnamed map parameters and results in mixed signatures such as ([]string, int, map[int]int, error), allowing function patterns to match those signatures.\n  - Go correctly represents chained indexing such as table[key][next] as nested index expressions, restoring matches for nested-index patterns.\n\n  (go-v0.25.0)\n- julia grammar update (v0.25.0):\n\n  - Julia source parsing and rule patterns now support public API declarations while distinguishing them from export declarations and calls named public.\n  - Julia source parsing and rule patterns now support outer-qualified loop bindings, preserving their distinction from ordinary bindings and a variable named outer.\n  - Julia parsing and matching now support typed const fields without initializers in mutable structs.\n  - Julia source parsing and rule patterns now support renaming imported macros, such as import A: @m as @n and import A: @m as @B.n, and keep the @ on macro names in imports, exports, and public declarations.\n  - Julia rules can now match unary ± expressions and distinguish binary ± from ∓, reducing operator-related false positives.\n  - Julia numeral juxtaposition such as 1__2 is now represented as multiplication by __2 and can be found by multiplication patterns.\n  - Julia function-definition patterns now retain where constraints, avoiding matches against definitions with a different constraint.\n\n  (julia-v0.25.0)\n\n### ### Fixed\n\n- OCaml: taint analysis now follows data through expression statements and\n  sequence expressions. For example, in `let x = (r := 1; source ()) in sink x`,\n  the value of the sequence is the result of `source ()`, so the finding on\n  `sink x` is now reported. Taint also no longer leaks from one `match` case\n  into the next one. (ocaml-expression-statements)\n- OCaml: the last expression of a function body is now treated as the function's result, so taint flows through calls. (ocaml-implicit-returns)\n- Semgrep no longer logs credentials embedded in a proxy URL (for example\n  `HTTPS_PROXY=http://user:password@proxy:8080`) when it reports the configured\n  proxy settings. (proxy-log-redact-userinf","is_prerelease":false},"readme":true,"readme_zh":false,"news":[],"stale":false,"snapshot_at":"2026-11-16T09:23:14Z","history_start":"2026-09-06"}