chore(deps): update dependency semgrep to v1.118.0 #5126
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
1.116.0
->1.118.0
Warning
Some dependencies could not be looked up. Check the Dependency Dashboard for more information.
Release Notes
returntocorp/semgrep (semgrep)
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
that start with
./
. For example, the pattern./*.py
should be written as/*.py
to have the desired effect of excluding the.py
fileslocated in the same directory as the
.semgrepignore
file containingthe pattern.
To minimize surprises for users switching to Semgrepignore v2,
we'll be interpreting automatically
./*.py
as/*.py
for the timebeing so as to match the legacy Semgrepignore v1 behavior. Users should not
rely on this since it doesn't comply with the Gitignore/Semgrepignore
standard and will be removed in the future. (tolerate-semgrepignore-v1-dotslash)
Semgrepignore v2 by default. This brings the behavior of the Semgrepignore file
exclusions closer to Git and
.gitignore
files. There can nowbe multiple
.semgrepignore
files in the project. The.semgrepignore
filein the current folder is no longer consulted unless it in the project.
Negated patterns are now supported such as
!scanme.py
as with Gitignore.Some bugs were fixed. (use-semgrepignore-v2)
Changed
Fixed
*
and?
to match file names with a leading period. This matches the behavior of Gitignore and Semgrepignore v1. (semgrepignore-dotfiles)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.