Skip to content

Commit

Permalink
Add license scan report and status (#3847)
Browse files Browse the repository at this point in the history
Signed off by: fossabot <[email protected]>
  • Loading branch information
fossabot authored Jan 21, 2025
1 parent ff26b24 commit b247a91
Showing 1 changed file with 5 additions and 1 deletion.
6 changes: 5 additions & 1 deletion README.md
Original file line number Diff line number Diff line change
Expand Up @@ -4,6 +4,7 @@
[![Maven Central](https://maven-badges.herokuapp.com/maven-central/io.camunda.connector/connector-core/badge.svg?style=flat)](https://maven-badges.herokuapp.com/maven-central/io.camunda.connector/connector-core)
[![Outbound template](https://img.shields.io/badge/outbound_connector-use_template-blue)](https://github.com/camunda/connector-template-outbound)
[![Inbound template](https://img.shields.io/badge/inbound_connector-use_template-blue)](https://github.com/camunda/connector-template-inbound)
[![FOSSA Status](https://app.fossa.com/api/projects/git%2Bgithub.com%2Fcamunda%2Fconnectors.svg?type=shield)](https://app.fossa.com/projects/git%2Bgithub.com%2Fcamunda%2Fconnectors?ref=badge_shield)

This is the repository for Camunda Connectors. It manages all parts of the Connectors ecosystem,
including the Connector SDK, out-of-the-box Connectors available in Camunda, the Connector Runtime, and the Docker images.
Expand All @@ -27,6 +28,9 @@ For more information on Connectors, refer to the

This is a multi-module project with different licenses applied to different modules.


[![FOSSA Status](https://app.fossa.com/api/projects/git%2Bgithub.com%2Fcamunda%2Fconnectors.svg?type=large)](https://app.fossa.com/projects/git%2Bgithub.com%2Fcamunda%2Fconnectors?ref=badge_large)

### Modules available under [Apache 2.0 license](https://www.apache.org/licenses/LICENSE-2.0)

* [Connector SDK](connector-sdk) including all supporting libraries
Expand Down Expand Up @@ -166,4 +170,4 @@ mvn clean package
We use [backport-action](https://github.com/korthout/backport-action) to backport PRs to older releases.
For example, add a label `backport release/8.3` to backport a PR to the `release/8.3` branch. This will take effect when the PR is meged.

You can also trigger this for already merged PRs by posting a comment on the PR containing `/backport`.
You can also trigger this for already merged PRs by posting a comment on the PR containing `/backport`.

0 comments on commit b247a91

Please sign in to comment.