Details
-
Epic
-
Status: In Progress
-
Highest
-
Resolution: Unresolved
-
None
-
Update vulnerable direct dependencies
-
Best Practice (global - all code)
-
1
-
Not required
-
Original Scope
-
XS
-
GO
-
GO
-
GO
Description
Description of Use Case / Requirement:
Each project will update the vulnerable direct dependencies in their code base following the recommendations of SECCOM documented in individual project pages under Honolulu Package Updates in the protected Security Vulnerabilities space.
Each project should reference their page for the policy description and correlation with ONAP release milestones.
Submit a LF Ticket for access to the Security Vulnerabilities space.
Owners (one of these should be the Assignee - use @ notation): zwarico , Pawel_P
Link to HLD/LLD (if any):
Dependency Relationships with Other Projects:
Project Impact (Test Only (TO), Code (C)): C **
Support Status for each Affected Project (Supported (S); Partially Supported (P); Not Supported (N)):
Note: for any affected projects labeled 'P' or 'N', please document the resulting gaps.
Integration Leads (use @ notation):
Company Engagement:
Attachments
Issue Links
- clones
-
REQ-323
Each project will update the vulnerable direct dependencies in their code base
-
- Done
-
- is blocked by
-
REQ-863 PACKAGES UPGRADES IN DIRECT DEPENDENCIES FOR ISTANBUL
-
- In Progress
-
-
ONAPARC-656
(Honolulu-R8) - NF - CONTINUATION OF PACKAGES UPGRADES IN DIRECT DEPENDENCIES
-
- Closed
-
-
-
- To Do
-
- relates to
-
DCAEGEN2-2551
REQ-439 DCAE Vulnerability updates for Honolulu
-
- Closed
-
-
MODELING-525
continuation of packages upgrades in direct dependencies
-
- Closed
-
-
-
- Closed
-
-
VFC-1849
continuation of packages upgrades in direct dependencies
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
- mentioned in
-
Page Loading...
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-