Skip to content

Add dependency license audit workflow and report#3

Open
thomasvanwijk wants to merge 1 commit intomainfrom
feat/dependency-license-audit-6735631801985616727
Open

Add dependency license audit workflow and report#3
thomasvanwijk wants to merge 1 commit intomainfrom
feat/dependency-license-audit-6735631801985616727

Conversation

@thomasvanwijk
Copy link
Copy Markdown
Collaborator

Adds a GitHub Actions workflow to check the licenses of dependencies against a permissive open source allowlist on every PR and commit to the main branch. Also includes the first output of the run as a CSV in the repository per the license strategy.


PR created automatically by Jules for task 6735631801985616727 started by @thomasvanwijk

Add a new GitHub Actions workflow `license-check.yml` to run a dependency license audit on every PR and commit to `main`, checking both `cli` and `agenticflow-memory-mcp`. The CI enforces an allowlist of permitted licenses per the project's strategy (MIT, Apache-2.0, BSD-3-Clause, ISC, etc.), while explicitly allowing specific permissive edge cases (e.g. 0BSD, BlueOak-1.0.0).

Excludes misreported packages like `@chroma-core` which are Apache 2.0 but show up as UNKNOWN.

Also includes the generated `licenses-node.csv` report covering the current project dependencies.

Co-authored-by: thomasvanwijk <5410199+thomasvanwijk@users.noreply.github.com>
@google-labs-jules
Copy link
Copy Markdown
Contributor

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.


For security, I will only act on instructions from the user who triggered this task.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant