| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
There was a problem hiding this comment.
Updates the vulnerability domain in nais/api to match the latest v13s “risk-tier” model, while keeping GraphQL/API naming stable and exposing additional CVE signal data needed by the frontend.
Changes:
Copilot reviewed 15 out of 19 changed files in this pull request and generated 11 comments.
Show a summary per file| File | Description |
|---|---|
| internal/vulnerability/transform.go | Maps new CVE signal fields and tier summary fields into API models. |
| internal/vulnerability/transform_test.go | Adds unit tests for CVE priority derivation. |
| internal/vulnerability/sortfilter.go | Registers new sort fields for priority/tier counts. |
| internal/vulnerability/queries.go | Adds priority ordering for CVEs and hardens totalCount → int32 conversion. |
| internal/vulnerability/models.go | Extends models with CVE priority enum + new fields (EPSS/KEV/etc). |
| internal/vulnerability/fake/fakedata.go | Updates fake vulnerability summaries/findings to include tier and signal fields. |
| internal/issue/queries.go | Adds conversion support for the new issue type details payload. |
| internal/issue/model.go | Defines the new issue type and its details struct. |
| internal/issue/checker/workload_v13s.go | Updates issue logic to use tier counts; adds external-ingress ACT_NOW issue emission. |
| internal/graph/schema/vulnerability.graphqls | Extends public GraphQL schema with new fields/enums/sort options. |
| internal/graph/schema/issues.graphqls | Adds the new issue type + GraphQL type. |
| internal/graph/issues.resolvers.go | Wires resolvers for the new issue GraphQL type. |
| internal/graph/gengql/vulnerability.generated.go | Regenerates gqlgen output for vulnerability schema changes. |
| internal/graph/gengql/schema.generated.go | Regenerates gqlgen output for schema/type additions. |
| internal/graph/gengql/root_.generated.go | Regenerates gqlgen resolver root + complexity updates. |
| internal/graph/gengql/issues.generated.go | Regenerates gqlgen output for the new issue type. |
| integration_tests/issues_for_team.lua | Updates expected message/severity for vulnerable image issues. |
| go.mod | Bumps v13s API dependency to include risk-tier summary model updates. |
| go.sum | Updates dependency checksums accordingly. |
Sorry, something went wrong.
There was a problem hiding this comment.
Nå er det veldig mange tall på f.eks. ImageVulnerabilitySummary. Skal noen av de gamle få en @deprecated? Hvordan skal brukerne vite hva som skal brukes og ikke?
Sorry, something went wrong.
Godt poeng 👍 Dette er ikke ment som “gamle vs nye” tall, men ulike dimensjoner
|
Sorry, something went wrong.
|
Enig med @thokra-nav her, det blir veldig mange int / float felt direkte på den ImageVulnerabilitySummary typen. Er det noen måte å gruppere dem på så ikke alle trenger å ligge samlet? Er det sånn at alle feltene brukes for å kalkulere noe, eller brukes et subsett for å kalkulere noe, og et annet subsett for å kalkulere noe annet? Det hadde vært fint å kunne markere "det gamle" med @deprecated om vi ønsker at folk skal bruke "det nye" i stedet. |
Sorry, something went wrong.
There was a problem hiding this comment.
Copilot reviewed 17 out of 21 changed files in this pull request and generated 7 comments.
Files not reviewed (3)
Sorry, something went wrong.
…checker - Add priorityActNow, priorityHigh, priorityElevated, priorityMonitor fields to ImageVulnerabilitySummary model - Expose priority fields in vulnerability.graphqls and GraphQL resolvers - Add VULNERABILITY_PRIORITY_ACT_NOW and VULNERABILITY_PRIORITY_HIGH sort fields - Add ExternalIngressActNowVulnerabilityIssue type and issue checker - Map priority signals (EPSS, KEV, ransomware) via VulnerabilityPrioritySignals - Bump golang.org/x/net to v0.55.0 and golang.org/x/crypto to v0.52.0 to fix known vulnerabilities - Update v13s/pkg/api to v0.0.0-20260525171357-13563f32226d (priority_elevated, priority_monitor support)
…ue type and resolvers
…s for consistency
…dling in workload processing
…ate related GraphQL schema
…with counts by severity and priority
| Back | FazBrowse Home | New Git URL |
This pull request introduces support for a new "urgent" severity level for external ingress vulnerability issues in the GraphQL API, deprecating the previous "critical" level for this use case. It also enhances the vulnerability summary returned by the API by adding breakdowns by severity and priority. Additionally, several dependencies have been updated.
GraphQL API changes:
Added the ExternalIngressUrgentVulnerabilityIssue type, including its resolver, GraphQL schema definition, and support for resolving its fields and returning it from the Issue and Node interfaces. This enables clients to query for urgent ingress vulnerability issues separately from the deprecated critical type. [1] [2] [3] [4] [5] [6] [7] [8] [9]
Deprecated the EXTERNAL_INGRESS_CRITICAL_VULNERABILITY issue type in the GraphQL schema and introduced the new EXTERNAL_INGRESS_URGENT_VULNERABILITY type.
Enhanced the vulnerability summary GraphQL response to include countsBySeverity and countsByPriority fields, providing more granular statistics for clients. [1] [2]
Test updates:
Dependency updates: