Add UI for durable component license curation: audit panel, component policies, read-only imported components - #1743
Open
canikrichard wants to merge 4 commits into
Open
Conversation
Component rows expand like findings rows: audit trail, comments, license override (SPDX ID or custom license name, or an SPDX expression) and a free-text details note, backed by the component analyses v2 API. Curation controls require POLICY_MANAGEMENT. Part 3 of the component audit panel feature (brightpick fork). Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Signed-off-by: Richard Canik <canik@brightpick.ai>
Policy Management gains a Component Policies tab: list plus create/edit/delete modal (name, enabled, priority, CEL condition, license override select, details). Server-side CEL/license validation errors surface as toasts. Part 5 of the component audit panel feature (brightpick fork). Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Signed-off-by: Richard Canik <canik@brightpick.ai>
Components imported from BOM uploads are read-only in the UI: the details modal hides its Update and Delete buttons and renders all fields disabled for them. Manually created components remain fully editable, and the Add Component action stays available.
The v2 endpoints follow the API's naming conventions: request and response properties are snake_case, updates respond 204 without a body, and creations respond 201 with a Location header. The audit panel re-fetches the analysis after saving instead of reading the response.
✅ Snyk checks have passed. No issues have been found so far.
💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse. |
canikrichard
changed the title
canikrichard
marked this pull request as ready for review
August 12, 2026 10:24
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
UI for durable component license curation, the frontend counterpart of DependencyTrack/dependency-track#6961:
All new UI strings go through i18n (
message.component_policiesadded to every locale file; other labels reuse existing keys).Addressed Issue
Frontend part of DependencyTrack/dependency-track#251 (see DependencyTrack/dependency-track#6961 for the API server part — the design is recorded in ADR 036 included there).
Additional Details
/component-analyses(+ comments) and/component-policies.policy_priority_highest/high/normal/low) rather than introducing new terms.vue-i18n-extract report --cireports zero missing keys, and the production build succeeds.Checklist