-
Notifications
You must be signed in to change notification settings - Fork 40
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Audit needed for the Hashicorp MPL -> BUSL license change #305
Comments
It seems that This was the dep graph for them in the event-generator (before I fixed it):
I had to reset the |
I am doing the same (ie: switching to new go and running
Consul is no more greppable in them. |
With #347, all tasks are done now! |
@leogr: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
We've conducted an initial scan following the CNCF input request after the Hashicorp MPL -> BUSL license change.
The lists below were generated after examining the
go.sum
packages across the entire Falcosecurity organization.From this initial audit, we've determined that we are NOT using any BUSL-licensed packages 🥳 Thus, we are unaffected by the MPL -> BUSL license transition, which is positive.
Additionally, we identified some Hashicorp packages under MPL 2.0 that we are using without a CNCF Governing Board exception.
For context, according to the CNCF IP Policy, all 3rd-party dependencies must either be Apache 2.0 licensed OR listed in the Approved Licenses for Allowlist OR have an exception approved by the Governing Board (see already approved license exceptions).
MPL2'd packages being used without an exception
[ACTION NEEDED]! @falcosecurity/core-maintainers
cc @falcosecurity/driverkit-maintainers @falcosecurity/event-generator-maintainers @falcosecurity/falcoctl-maintainers @falcosecurity/falcosidekick-maintainers @falcosecurity/kilt-maintainers @falcosecurity/plugins-maintainers
Please carefully evaluate the possibility of removal for these Go dependencies listed in the table below. If that's not feasible, we must submit a ticket to the CNCF for review and request a license exception (I can take care of that once we have completed the evaluation of them one by one).
It's worth noting that some of these packages might not be in active use. A straightforward cleanup might suffice to remove them:
falcosidekickpluginsevent-generatorfalcoctlfalcosidekickpluginsevent-generatorfalcoctlfalcosidekickpluginsCleanups in progress
go get -u
falcoctl#315Already allowed Hashicorp packages.
The packages listed below are already permitted, either due to inclusion in the allowlist or because they have a GB-approved exception. Therefore, no additional action is required. We can continue to use them without concerns.
The text was updated successfully, but these errors were encountered: