Describe the problem

when executing an inspec profile from a remote repository with a default branch not named master the following error is returned.

inspec exec https://github.com/org/profile.git

Profile git dependency failed - unable to resolve ma

Describe the bug
This resource causes the error WARNING: skipped AWS017 check due to error(s): value is null

And it happens even if I try to explicit skip AWS017 from cli:

tfsec --exclude AWS017
WARNING: skipped AWS017 check due to error(s): value is null

tfs

Check to confirm CloudTrail is configured for multi-region.

CloudFormation - IsMultiRegionTrail: https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-cloudtrail-trail.html

There are about ~240 URLs and licenses listed at https://directory.fsf.org/wiki?title=Category:License
We should:

1. ensure that we can detect all of them
2. ensure that we can detect their URL
   We should also add as an "other_urls" ech URL to the corresponding license YAML

fsf-license-urls.txt

We should make it easier to install this plugin.

Describe the ideal solution

We need a new endpoint that functions as getIntegrationById endpoint.

Describe your use cases

We currently fetching all integration via appsync (or more specifically a sub-category of integrations based on integrationType) and iterate until we find one that matches the integrationId passed.

How frequently would you use such feature

Although, we

Description

In rest-api, the reuse component has a mandatory parameter reuse_group of type integer which expects group id. But there is no endpoint available to get a group id from the group name.

How to reproduce

Most of the endpoints have group parameter that expects group name of type string. But for the reuse component which has parameter reuse_group, expects group id of typ

The code at

https://github.com/oss-review-toolkit/ort/blob/fd1b62a799523b55871cd04001ddfe1e6262da0f/analyzer/src/main/kotlin/managers/Stack.kt#L113-L140

can be simplified now that Stack 2.3.1 supports ls dependencies json.

Description

Currently add_failure takes the values required to create a failure, creates it then adds it to the Result object's failed_rules
On the other hand add_warning takes a Failure object directly.

Proposed solution

The methods should be updated so that they both have the same behavior (or maybe even just add an add_finding method which takes a type that can be either Failure o