wkoot

Results 20 issues of wkoot

Change `SoftwareProductInstallation.render_type` to property, so filtering and sorting works the same throughout. Now, the same logic is particularly reimplemented in tables.py `order_type`

enhancement

In the github release workflow, we have an Anchore SBOM Action that doesn't seem to be used further. The SBOM that this action produces, should be pushed to Docker Hub...

- [ ] Change the default `PROXY_PORT` to `8080`, so we don't bind a privileged port. Since this will remove backwards compatability and changes to docker-compose, it requires a major...

Deployment platform

Fixes #540, #677

breaking change

It seems that deserialization silently loads broken bom data, omitting components due to deduplication. For reproduction, refer to the sample testdata output as produced in https://github.com/CycloneDX/cyclonedx-cli/issues/399: ```json { "bomFormat": "CycloneDX",...

bug
help wanted
question

### Proposed Changes Either rename `views.generic.BulkImportView` to `views.generic.ImportView`, or alter the urlpatterns to `name='*_bulk_import'`. For backwards compatability, the `BulkView` could be an alias or urlpattern `name='*_import'` could be supported until...

type: housekeeping

Version `cyclonedx-cli:0.27.1`, CycloneDX format 1.6 When trying to validate sbom that was produced with `cyclonedx-cli merge`, I get the following errors: ``` \"$.vulnerabilities[244].ratings[8].method: does not have a value in the...

Given the following two test files, their merged output does not deduplicate components as mentioned in https://github.com/CycloneDX/cyclonedx-python-lib/issues/540#issuecomment-2343195560 File `test/in1.json`: ```json { "$schema": "http://cyclonedx.org/schema/bom-1.5.schema.json", "bomFormat": "CycloneDX", "specVersion": "1.5", "metadata": {"component": {"bom-ref":...

**Describe the bug** The dropdown "apply change to X" is partially displayed outside the screen space. When the column is on the left, the menu expands to the left, when...

Bug

**Describe the bug** The health endpoint is not actually an endpoint, it just happens to return http 200 ok like any api url path. **To Reproduce** 1. Navigate to `/api/health`...

Bug