lix-community/nix-security-tracker
0
0
Fork 0
Code Issues 94 Pull requests 9 Projects Releases Packages Wiki Activity

Remove affected channels from matching suggestions #419

New issue
Open
opened 2024-12-05 12:25:48 +00:00 by fricklerhandwerk · 0 comments
fricklerhandwerk commented 2024-12-05 12:25:48 +00:00 (Migrated from github.com)
Copy link

Since we check version constraints, it could that a package is affected in one Nixpkgs release but not another. As a security team member triaging matching suggestions, I want to be able to remove unaffected releases from a package entry.

Implementation note: We probably want to only strike through/grey out "removed" channels, because it should stay evident why those aren't present. If they disappear entirely it would look like they're missing from evaluation data.

Since we check version constraints, it could that a package is affected in one Nixpkgs release but not another. As a security team member triaging matching suggestions, I want to be able to remove unaffected releases from a package entry. Implementation note: We probably want to only strike through/grey out "removed" channels, because it should stay evident why those aren't present. If they disappear entirely it would look like they're missing from evaluation data.
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
npins-auto-update
No results found.
Labels
Clear labels   
automation

   
backend

something the web server needs to provide the frontend with

  
bug

Something isn't working

  
contributor experience

   
data

something about quality or quantity of ingested data

  
deployment

   
documentation

Improvements or additions to documentation

  
duplicate

This issue or pull request already exists

  
good first issue

Good for newcomers

  
help wanted

Extra attention is needed

  
nice to have

Nice to have, but not necessary for the time being

  
notifications

   
package maintainer

user story for package maintainers

  
performance

   
skin

Anything related to the visual presentation

  
tech debt

Activities that reduce tech debt

  
user story

description or implementation of a workflow

No labels
automation
backend
bug
contributor experience
data
deployment
documentation
duplicate
good first issue
help wanted
nice to have
notifications
package maintainer
performance
skin
tech debt
user story
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: lix-community/nix-security-tracker#419
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?