-
-
Notifications
You must be signed in to change notification settings - Fork 261
chore(deps): update dependency semgrep to v1.128.1 #5126
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
🦙 MegaLinter status:
|
e67dde2
to
1a8292a
Compare
1a8292a
to
ee49fee
Compare
ee49fee
to
75e6b25
Compare
75e6b25
to
f85ff7b
Compare
edccf06
to
aef5c62
Compare
aef5c62
to
6d1627e
Compare
This pull request has been automatically marked as stale because it has not had recent activity. If you think this pull request should stay open, please remove the |
98d3f45
to
badbb7b
Compare
This PR contains the following updates:
1.116.0
->1.128.1
Release Notes
returntocorp/semgrep (semgrep)
v1.128.1
No significant changes.
v1.128.0
Added
HTTP{,S}_PROXY=...
now accepts URIs without a scheme (e.gHTTP_PROXY=domain.com:port
) (saf-2082)Fixed
class $A
partial class pattern, in favor ofv1.127.1
Fixed
--trace
was passed and thenumber of jobs was greater than 1
v1.127.0
Compare Source
Fixed
TS configs. (code-8678)
v1.126.0
Compare Source
Fixed
v1.125.0
Added
--json
. (SC-2458)Fixed
.semgrepignore
excludes to be applied to Secrets product scans. Now, Semgrep will once again scan files that have been excluded from Code and SSC scans for possible leaked secrets. (SAF-2067)are now sorted correctly based on their location within files.
This benefits all the Semgrep IDE extensions (VSCode, IntelliJ). (ide-findings-order)
semgrep ci
logs in GitLab would return an incorrect URLwith the wrong
&ref=...
argument. (saf-959)v1.124.1
Fixed
.semgrepignore
excludes to be applied to Secrets product scans. Now, Semgrep will once again scan files that have been excluded from Code and SSC scans for possible leaked secrets. (SAF-2067)v1.124.0
Compare Source
Added
ALL_PROXY
,HTTP_PROXY
,HTTPS_PROXY
,NO_PROXY
,PROXY_USERNAME
andPROXY_PASSWORD
for all networking (includingthat done via the OCaml components). Moreover, the environment variable
OCAML_EXTRA_CA_CERTS
should now allow additional CA certs to be used fornetwork operations done by OCaml components. (code-8157)
Fixed
build.gradle.kts
files asbuild.gradle
. (SC-2209)with a
requires:
of the formnot A
, could produce findings with an emptylist of traces, potentially causing a crash. We now recognize the issue and
prevent the crash from happening. (code-8531)
f""
was not matched by the pattern "...". (gh-10047)metavariable-type
. Concretely, "2 * groups" was not considered an int, where groups is an int. Additionally adds type inference for mod, floor division, and pow. (gh-9855)disproportionate amount of time significantly slowing down scans. (saf-1978)
v1.123.0
Compare Source
Fixed
v1.122.0
Compare Source
Added
Fixed
pro: Fixed inter-file naming bug affecting Go's struct-methods that could result
in false negatives.
Previously, adding a
pattern-inside
liketo a taint rule could cause some findings to incorrectly stop being reported. (code-7767)
PRO: Fixed the issue with type matching when a type has a type parameter, e.g., matching the pattern
std::vector<$T>
with the codestd::vector<int> v
in C++. (code-8443)Make Nuget dependency child parsing case insensitive (sc-2355)
Fixed bug where direct dev depenencies were not marked as direct when parsing package-lock.json projects. (sc-dev)
v1.121.0
Added
tsconfig.json
in instances where multipletypescript "projects" (i.e., separately rooted source directories with their
own configurations not joined by a single
tsconfig.json
with projectreferences) are being scanned as one project under semgrep. This should result
in better name/module resolution in TypeScript. (code-7798)
include
,exclude
andfiles
properties intsconfig.json
. Projects which use more than one tsconfig in a given directorywhich apply to different sets of files under that directory should see
improvements in name/module resolution. (code-7798-a)
Changed
Fixed
--disable-nosem
was not properly causing nosemgrep'd findingsto be uploaded to the App. (saf-1982)
This fixes a regression introduced in 1.117.0 (sca-1705). (sc-1705)
v1.120.1
Fixed
-j1
and it can be overridden by the user. (interfile-num-jobs)v1.120.0
Compare Source
Added
(e.g., _cargo, _opam, .svn) (semgrepignore)
--x-semgrepignore-filename
to change the name of.semgrepignore
files to something else. This can be used to scan a subproject in a separate semgrep invocation as the rest of the containing project. (semgrepignore-filename)Fixed
-j
setting so as to take into account the cgroupCPU quota on Linux. This will affect Docker and other containerized
environments that share resources on the same host. Use the new command
semgrep show resources --experimental
to show the default setting. (saf-1950)v1.119.0
Compare Source
Added
semgrep show project-root
is now provided to displaythe project root path associated with a scan root. This is useful for
troubleshooting Semgrepignore (v2) issues. (saf-1936)
Fixed
tainting: Apply
taint_assume_safe_numbers
andtaint_assume_safe_booleans
earlier when considering to track taint through class fields and function
parameters. If the field/parameter has a number/Boolean type and the
corresponding option is set, it will just not be tracked. In some cases this
can help with performance.
Also added
short
/Short
to the list of integer types recognized bytaint_assume_safe_numbers
. (code-8345)IDE: The Semgrep VS Code Extension will no longer hang on
Getting code actions from Semgrep...
on saving a file, when updating rules. (saf-1954)
v1.118.0
Compare Source
Fixed
Pro: Failure to parse a
package.json
file when analysing JavaScript orTypeScript is no longer a fatal error. (code-8227)
taint-mode: Fixed bug in taint "auto-cleaning" where we automatically clean the
LHS of an assigmnet if the RHS is clean, provided that the LHS is not subject to
any "side-effects". In some cases, this could cause the taint analysis to timeout.
Some combinations of rules and repos will see a major perf improvement, in other
cases it may not be noticeable. (code-8288)
In a Semgrep rule's
metadata
section, two fields may provide URLs:source
: populated dynamically by the Semgrep registry serving the rule, it's a URL thatoffers information about the rule.
source-rule-url
: optional string, a URL for the source of inspiration for the rule.The SARIF format supports only one URL under the field
helpUri
.Previously, Semgrep populated the SARIF
helpUri
field only withmetadata.source
.This fix is to use
metadata.source
if available, otherwise falling back tometadata.source-rule-url
.Contributed by @candrews. (gh-10891)
v1.117.0
Compare Source
Added
--json
. (SC-2458)Fixed
.semgrepignore
excludes to be applied to Secrets product scans. Now, Semgrep will once again scan files that have been excluded from Code and SSC scans for possible leaked secrets. (SAF-2067)are now sorted correctly based on their location within files.
This benefits all the Semgrep IDE extensions (VSCode, IntelliJ). (ide-findings-order)
semgrep ci
logs in GitLab would return an incorrect URLwith the wrong
&ref=...
argument. (saf-959)Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.