# US 2026/0037246 A1 · Automatically updating software components

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2026/0037246 A1
- Document ID: US20260037246A1
- Status: Published application
- Kind: A1
- Application number: 18/794,332
- Filed: 2024-08-05
- Published: 2026-02-05
- Earliest claimed: 2024-08-05
- Assignees: Dell Products L.P.
- Applicants: Dell Products L.P.
- Inventors: Shi Kai Khiew; Robin Kedia; Antony Prabakaran Jayaveeran; Hao Yu Feng; Sneha Vijay
- Web page: https://patentgrep.com/patent/US20260037246A1

## CPC

- G06F 8/65: Updates (security arrangements therefor G06F21/57)
- G06F 21/577: {Assessing vulnerabilities and evaluating computer system security}
- G06F 2221/033: Test or assess software
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

Methods, apparatus, and processor-readable storage media for automatically updating software components are provided herein. An example computer-implemented method includes identifying, by at least one processing device of a computing platform, a release of an updated version of a software component of a software project and obtaining one or more of vulnerability information for the software component and license information associated with the software component. The method includes generating an upgrade score for the software component based on at least a portion of one or more of the obtained vulnerability information and the obtained license information and determining, by the at least one processing device, whether to upgrade the component to the updated version based at least in part on the upgrade score. The method also includes initiating one or more automated actions based at least in part on a result of the determining.

## Claims

### Claim 1

A computer-implemented method comprising:
identifying, by at least one processing device of a computing platform, a release of an updated version of at least one software component of a software project;
obtaining one or more of: vulnerability information for the at least one software component and license information associated with the at least one software component;
generating an upgrade score for the at least one software component based on at least a portion of one or more of the obtained vulnerability information and the obtained license information;
determining, by the at least one processing device, whether to upgrade the at least one software component to the updated version based at least in part on the upgrade score; and
initiating one or more automated actions based at least in part on a result of the determining;
wherein the method is performed by the at least one processing device comprising a processor coupled to a memory.

### Claim 2 (depends on 1)

The computer-implemented method of claim 1, wherein a plurality of security scanners generates the vulnerability information and wherein the plurality of security scanners comprises at least two distinct security scanner tools operating on separate processing platforms.

### Claim 3 (depends on 1)

The computer-implemented method of claim 1, wherein the one or more automated actions comprise at least one of:
updating the at least one software component to the updated version;
deploying the updated version of the at least one software component to one or more computing environments; and
providing the upgrade score and information related to the at least one software component to an interactive dashboard.

### Claim 4 (depends on 1)

The computer-implemented method of claim 1, wherein the vulnerability information is obtained for a plurality of versions of the at least one software component and comprises a respective vulnerability count for each of two or more vulnerability severity levels.

### Claim 5 (depends on 4)

The computer-implemented method of claim 4, wherein the generating the upgrade score comprises comparing the vulnerability information across multiple previous versions of the at least one software component.

### Claim 6 (depends on 4)

The computer-implemented method of claim 4, wherein the upgrade score is further based on version information obtained from one or more online sources, wherein the version information comprises:
release dates corresponding to respective ones of the plurality of versions of the at least one software component;
release notes corresponding to respective ones of the plurality of versions of the at least one software component; and
issue tracking information corresponding to respective ones of the plurality of versions of the at least one software component.

### Claim 7 (depends on 1)

The computer-implemented method of claim 1, further comprising:
performing one or more of unit testing and integration testing for the updated version of the at least one software component; and
adjusting the upgrade score based at least in part on a result of the one or more of the unit testing and the integration testing.

### Claim 8 (depends on 1)

The computer-implemented method of claim 1, wherein the generating the upgrade score comprises comparing the license information to one or more license criteria maintained by an organization associated with the software project.

### Claim 9

A non-transitory processor-readable storage medium having stored therein program code of one or more software programs, wherein the program code when executed by at least one processing device causes the at least one processing device:
to identify, by the at least one processing device, a release of an updated version of at least one software component of a software project;
to obtain one or more of: vulnerability information for the at least one software component and license information associated with the at least one software component;
to generate an upgrade score for the at least one software component based on at least a portion of one or more of the obtained vulnerability information and the obtained license information;
to determine, by the at least one processing device, whether to upgrade the at least one software component to the updated version based at least in part on the upgrade score; and
to initiate one or more automated actions based at least in part on a result of the determining.

### Claim 10 (depends on 9)

The non-transitory processor-readable storage medium of claim 9, wherein a plurality of security scanners generates the vulnerability information and wherein the plurality of security scanners comprises at least two distinct security scanner tools operating on separate processing platforms.

### Claim 11 (depends on 9)

The non-transitory processor-readable storage medium of claim 9, wherein the one or more automated actions comprise at least one of:
updating the at least one software component to the updated version;
deploying the updated version of the at least one software component to one or more computing environments; and
providing the upgrade score and information related to the at least one software component to an interactive dashboard.

### Claim 12 (depends on 9)

The non-transitory processor-readable storage medium of claim 9, wherein the vulnerability information is obtained for a plurality of versions of the at least one software component and comprises a respective vulnerability count for each of two or more vulnerability severity levels.

### Claim 13 (depends on 12)

The non-transitory processor-readable storage medium of claim 12, wherein the generating the upgrade score comprises comparing the vulnerability information across multiple previous versions of the at least one software component.

### Claim 14 (depends on 12)

The non-transitory processor-readable storage medium of claim 12, wherein the upgrade score is further based on version information obtained from one or more online sources, wherein the version information comprises:
release dates corresponding to respective ones of the plurality of versions of the at least one software component;
release notes corresponding to respective ones of the plurality of versions of the at least one software component; and
issue tracking information corresponding to respective ones of the plurality of versions of the at least one software component.

### Claim 15 (depends on 9)

The non-transitory processor-readable storage medium of claim 9, wherein the program code, when executed by the at least one processing device, further causes the at least one processing device:
to perform one or more of unit testing and integration testing for the updated version of the at least one software component; and
to adjust the upgrade score based at least in part on a result of the one or more of the unit testing and the integration testing.

### Claim 16

An apparatus comprising:
at least one processing device comprising a processor coupled to a memory;
the at least one processing device being configured:
to identify, by the at least one processing device, a release of an updated version of at least one software component of a software project;
to obtain one or more of: vulnerability information for the at least one software component and license information associated with the at least one software component;
to generate an upgrade score for the at least one software component based on at least a portion of one or more of the obtained vulnerability information and the obtained license information;
to determine, by the at least one processing device, whether to upgrade the at least one software component to the updated version based at least in part on the upgrade score; and
to initiate one or more automated actions based at least in part on a result of the determining.

### Claim 17 (depends on 16)

The apparatus of claim 16, wherein a plurality of security scanners generates the vulnerability information and wherein the plurality of security scanners comprises at least two distinct security scanner tools operating on separate processing platforms.

### Claim 18 (depends on 16)

The apparatus of claim 16, wherein the one or more automated actions comprise at least one of:
updating the at least one software component to the updated version;
deploying the updated version of the at least one software component to one or more computing environments; and
providing the upgrade score and information related to the at least one software component to an interactive dashboard.

### Claim 19 (depends on 16)

The apparatus of claim 16, wherein the vulnerability information is obtained for a plurality of versions of the at least one software component and comprises a respective vulnerability count for each of two or more vulnerability severity levels.

### Claim 20 (depends on 19)

The apparatus of claim 19, wherein the generating the upgrade score comprises comparing the vulnerability information across multiple previous versions of the at least one software component.
