Is your feature request related to a problem? Please describe.

I'm kicking the tires on changing our Gemfile to gems.rb. However, we have many internal gems within our monorepo and it just occurred to me that it would be cool to have a configurable cop that enforces one or the other.

Describe the solution you'd like

A cop that checks to make sure you have a Gemfile or a `gems.

Describe the bug

According to the SARIF spec, invocation should be the child of a run:

https://docs.oasis-open.org/sarif/sarif/v2.1.0/csprd01/sarif-v2.1.0-csprd01.html#_Toc10540933

Currently build_sarif_output is nesting it at the root of the document, which is producing SARIF which does not conform to the specification:

https://github.com/returntocorp/semgrep/blob/9a73a142dc

Affects PMD Version: 6.30.0-SNAPSHOT

Rule: UselessOverridingMethod

Description:

From pmd/pmd#2871 (comment)

Note: There seems to be a difference when having the class in the auxclasspath or not (typeresolution).

Code Sample demonstrating the issue:

e.g.

# map.py
def func(a: int) -> float:
    return float(a)

map(func, ['str'])

$ pytype map.py
Computing dependencies
Analyzing 1 sources with 0 local dependencies
ninja: Entering directory `/[redacted]/.pytype'
ninja: no work to do.
Success: no errors found

while

$ mypy map.py
map.py:5: error: Argument 1 to "map" has incompatible type "Ca

Describe the bug
In the docs found here:
https://bandit.readthedocs.io/en/latest/plugins/index.html#complete-test-plugin-listing

B109 and B111 show a description instead of a plugin name. This looks inconsistent since all the other plugin names are listed. I believe this is a result of a recent change to remove these deprecated plugins.

To Reproduce

1. Navigate to https://bandit

This file is enormous. Also, breaking it up will make running tests faster since Gradle can run separate test classes in parallel.

The Problem

With the new model-property type and ModelPropertyRule Larastan now has the ability to check the existence of model columns that are given to a method.

Adding the model-property type to the Laravel's core methods are done with the help of PHPstan stubs. Some [examples](https://github.com/nunomaduro/larastan/blob/master/stubs/Elo

I am looking for a list of visitors/detectors that I can omit. Specifically, I am look for the allowed values for https://spotbugs.github.io/spotbugs-maven-plugin/spotbugs-mojo.html#omitVisitors.
Previously, in SpotBugs 3.1, this list could be found under "detectors" at e.g. https://spotbugs-in-kengo-toda.readthedocs.io/en/lqc-list-detectors/detectors.html#standard-detectors, but that page/menu

I wrote some of the code to do this in a branch https://github.com/python-security/pyt/compare/class_based_views, but since I'm working on other things and this feature seems cool and important I'm making this issue 👍

Let me know if you would like any help in implementing.

Justification
When first loading RD CodeExplorer displays all nodes as expanded to show contents. If you have other projects (Personal Macro Workbook (PMW), Excel add ins (*.xlam), etc...) they can obscure the project you want to work on.

Description
Add ability to expand/collapse all project nodes to quickly find project you wish to work with.

Where to get started
TestExplore