static-analysis

Describe the bug
Update on Homebrew-core job is failing during release https://github.com/returntocorp/semgrep/runs/4889454978?check_suite_focus=true

This is because https://github.com/returntocorp/semgrep/blob/develop/.github/workflows/release.yml#L320 has hardcoded the version of python that is running and github action is no longer running 3.9.9 but is running 3.9.10

We should dynami

Many repositories need to fix, so please help if you like.

If you could help, it would be helpful if you could comment before starting the work not to overlapping.

Fix example

Run exit command after lint.

echo '::group:: Running golangci-lint with reviewdog 🐶 ...'
go

ReflectionProperty::setValue() and ReflectionProperty::getValue() are polymorphic. If you work on a static property you can omit the first parameter which is the object on which you want to access the property.

The following code is valid imho:

class MyReflectionProperty extends ReflectionProperty
{
    public function getValue(?object $object = null): mixed
    {
        ret

Expected Behavior of the rule

This rule has gone way beyond reporting unused member, and covers properties, parameters, and member functions.
I would suggest a split at least for parameters vs (properties + functions).

Context

This is triggered by reviewing #3417