l3montree-dev / l3montree-dev/devguard
The risk history overview should always reflect only the data status where data is available for all artifacts
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 161
- Forks
- 43
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 37
Description
The asset overview should display the risk history only up to the date for which risk history data is available for all artifacts. If risk history has been calculated for Artifact A as of the reference date of September 13, but no calculation is yet available for Artifact B as of September 13 (e.g., due to an error in the Asset Daemon pipeline), the risk history in the overview for the asset version should only display data up to September 12 -> the risk history overview, total count, etc., should always reflect only the data status where data is available for all artifacts. The date should be specified in such a way that the front end can display this discrepancy, e.g., “Aggregated data through September 12” or something similar.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are named. Start by locating the asset overview's risk-history aggregation and the data returned for the front end. Done means the overview, totals, and related values stop at the latest date available for every artifact, while exposing that aggregation date for display.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100