Automated back-propagation of a fix using a reproducible build, test, and validation process to create a patched artifact

A server comprising:

• one or more processors;
• and
• one or more non-transitory computer readable media storing instructions executable by the one or more processors to perform operations comprising:
• determining that project code in a development system references an older version of a component in a third-party library;
• determining that the older version of the component has a vulnerability;
• determining that a newer version of the component in the third-party library has a fix commit that addresses the vulnerability;
• determining code changes associated with the fix commit;
• determining a subset of the code changes associated with the fix commit that addresses the vulnerability;
• submitting, via a communication network, a pull request to create a branch in a developer platform;
• creating, in the branch, a patch based on the subset of the code changes associated with the fix commit;
• applying, in the branch, the patch to the older version of the component to create a patched component;
• validating, in the branch, the patch;
• and
• based on successfully validating the patch, building and uploading the patched component and information associated with the patch to a registry to enable a software developer to download and use the patched component.

One or more non-transitory computer readable media capable of storing instructions executable by one or more processors to perform operations comprising:

• determining that project code in a development system references an older version of a component in a third-party library;
• determining that the older version of the component has a vulnerability;
• determining that a newer version of the component in the third-party library has a fix commit that addresses the vulnerability;
• determining code changes associated with the fix commit;
• determining a subset of the code changes associated with the fix commit that addresses the vulnerability;
• submitting, through a communication network, a pull request to create a branch in a developer platform;
• creating, in the branch, a patch based on the subset of the code changes associated with the fix commit;
• applying, in the branch, the patch to the older version of the component to create a patched component;
• validating, in the branch, the patch;
• and
• based on successfully validating the patch, building and uploading the patched component and information associated with the patch to a registry to enable a software developer to download and use the patched component.