DependencyTrack / DependencyTrack/frontend
[bug]Component Details does not reflect `internal: true` returned by the v2 project-components API
- Dominant language
- Vue
- Stars
- 171
- Forks
- 250
- Avg merge
- 10h 56m
- Merged PRs (30d)
- 84
Description
### Current Behavior
The Components UI does not show a component as **Internal** even though the v2 project-components API returns `"internal": true` for the same component.
For example, the project Components page requests:
```text
GET /api/v2/projects/{projectId}/components?only_outdated=false&only_direct=false&sort_by=name&sort_direction=ASC&q=com.mypackage&expand=package_metadata&expand=metrics&limit=20
```
The response item contains:
```json
{
"group": "com.mypackage.example",
"name": "example-artifact",
"internal": true
}
```
However, opening the component details in the frontend shows the **Internal** checkbox/indicator as unchecked.
### Steps to Reproduce
1. Configure an Internal Components group/namespace regex that matches a Maven component group, `(.*com\.mypackage\..*|.*com\.foo\..*)`.
2. Import a BOM containing a matching Maven component, for example a component whose group is `com.mypackage.example`.
3. Open the project **Components** page and search for the component.
4. Inspect the v2 project-components API response and confirm that the component has `"internal": true`.
5. Open the component details in the UI and observe the **Internal** checkbox/indicator.
### Expected Behavior
When the v2 project-components API returns `"internal": true`, the Components page and component details should consistently display the component as Internal.
### Dependency-Track Frontend Version
5.x
### Browser
Other
### Browser Version
Brave
### Operating System
macOS
### Checklist
- [x] I have read and understand the [contributing guidelines](https://github.com/DependencyTrack/dependency-track/blob/main/CONTRIBUTING.md#filing-issues)
- [x] I have checked the [existing issues](https://github.com/DependencyTrack/frontend/issues) for whether this defect was already reported
Contributor guide
No contributing guide indexed for this repository
Research direction
Start at the project Components page and component details UI, then trace how the v2 project-components API response is mapped to the Internal checkbox or indicator. Reproduce with a Maven component whose response contains "internal": true, and confirm that both the Components page and details consistently display it as Internal.
Written by the indexing model from the issue text.
Assessment
- Domain
- api, frontend
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100