14 results about "Software build" patented technology

Discussed herein are devices, systems, machine-readable media, and methods for assessing a software build for a vulnerability, generating release recommendations, and implementing a remedial action to mitigate security risks. A method includes receiving a Software Bill of Materials (SBOM) that lists one or more libraries used in a software build, receiving a user-specified administration policy, generating an over overall provenance bundle from a metadata of the one or more libraries used in the software build, implementing a gradient boosted tree algorithm using both the overall provenance bundle and the user-specified administration policy to generate a software releasability recommendation, receiving the software releasability recommendation into a Large Language Model (LLM) to generate a recommendation report detailing one or more software vulnerabilities, and implementing the software releasability recommendation by releasing the software build or blocking the release of the software build based on the software releasability recommendation.

This application relates to the field of computer software technology, providing an image management method, system, and computing device. The method is applied to a computing device equipped with a software integration system, including: responding to a code repository corresponding to the software integration system receiving a commit instruction, detecting the change status of the image configuration file; the change status is used to identify whether any instruction text in the image configuration file has changed; if the change status is "changed," loading the changed image configuration file; generating an image build instruction based on each instruction text in the image configuration file; generating an image file according to the image build instruction; and storing the image file in the image repository of the software integration system. Based on this solution, the computing device utilizes changes to the image configuration file to trigger the automatic generation and updating of image files, decoupling the image file generation process from the software package delivery request, avoiding repeated image building for each package delivery, and improving software build efficiency.

Systems and methods are provided for automatically building software in a secure environment. A system includes a software development environment, having an associated security level. The software development environment generates an encrypted software module containing a software module and a cryptographic hash representing a content of the software module and provides it to a software repository. The software repository, in response to receipt of a build plan, decrypts the encrypted software module to recover the software module and the cryptographic hash representing the content of the software module, generates a new cryptographic hash for the software module, and verifies that the new cryptographic hash matches the cryptographic hash representing the content of the software module. A build environment receives the plurality of software modules from the software repository and generates a software build from the plurality of software modules based upon the build plan.

Techniques are provided for managing software artifact snapshot repositories using definition files. One method comprises obtaining a definition file for a software artifact snapshot repository to be created in association with a given software application, wherein the definition file comprises information characterizing software artifacts used by the given software application to be included in the software artifact snapshot repository; and creating the software artifact snapshot repository, using the definition file, with the one or more software artifacts, wherein a software build of the given software application obtains at least some of the software artifacts using the created software artifact snapshot repository. At least some of the software artifacts included in the software artifact snapshot repository may be automatically updated in response to determining that a content of the software artifact snapshot repository does not match a current version of the definition file.

The embodiment of the invention discloses an external formula editing component calling method and device for an artificial intelligence proposition, equipment and a storage medium. The external formula editing component calling method comprises the following steps: in response to a request of an application platform, creating an OLE container on the application platform, and creating a component identifier of an external formula editing component; the external formula editing component comprises a desktop formula editor component or a third-party office software built-in formula component; in response to a formula editing requirement of an application platform, obtaining a component identifier through the COM component registry; dynamically loading the external formula editing component into an OLE container based on the component identifier; and the function calling of the application platform on the external formula editing component is realized through the IIDspatch interface of the external formula editing component. By means of the mode, cross-platform calling of the external formula editing assembly is achieved, a user can call the external formula editing assembly on the application platform, operation is convenient and efficient, and the problem of formula errors caused by cross-platform use is avoided.

A software build tool system and method for generating and validating a software build for execution on a target hardware device of an embedded system. The system includes: a user interface subsystem configured for receiving build parameter data pertaining to software from a user; a build tool subsystem configured for receiving the build parameter data from the user interface subsystem and building the software to generate a software build for execution on a target hardware device of an embedded system; and a memory reporter subsystem configured for receiving the software build generated by the build tool subsystem and providing access to target hardware build validation data resulting from and / or used as a part of the software build during execution.

System and method for an in-vehicle network comprising a microcontroller unit (MCU) located within the vehicle, which includes an internal Ethernet switch and an auxiliary core manager, wherein the MCU hosts one or more software builds and the auxiliary core manager manages the internal Ethernet switch and the software builds. An external Ethernet switch located within the vehicle connects one or more ports of the internal Ethernet switch to one or more devices through one or more virtual local area networks (VLANs), wherein, upon a reflash event, the auxiliary core manager generates a VLAN configuration and filter rule for the internal switch that associates the software builds with the MCU ports based on a MAC and IP address of each MCU port.

A computer-implemented method according to one approach, is for customizing the selection of stages in a multi-stage software build. The computer-implemented method includes: using information associated with the multi-stage software build to develop situational context of the multi-stage software build. The situational context is converted into a build context and the build context is further converted into a number of build stages. Moreover, the build stages are automatically edited, and the edited stages are executed.

A method and apparatus of a device that builds a target using a plurality of processing units is described. In an exemplary embodiment, the device receives a build file for the target, where the build file identifies a plurality of dependencies and the first target is depended on a second target. In addition, the device generates a directed acyclic graph for the first target from the plurality of dependencies. Furthermore, the device transforms the directed acyclic graph by transforming the first set of dependencies to a second set of dependencies and the second set of dependency includes the first dependency that is from a first node in the first target to a second node of a second target. The device additionally identifies a plurality of independent executable tasks, where each of the plurality of independent executable tasks is executable without an unresolved dependency and at least one of the plurality of executable tasks is associated with the second set of dependencies of the transformed directed acyclic graph. The device further schedules the plurality of independent executable tasks on the plurality of processing units. In addition, the device concurrently executes the plurality of independent executable tasks.

The present invention relates to an artificial intelligence-driven autonomous governance system for compliance-aware software delivery in development and operations environments. The disclosed system is implemented as a dedicated governance device comprising policy ingestion units, deployment signal acquisition units, compliance analysis processors, deployment control units, and secure audit storage units that collectively operate to monitor, evaluate, and enforce regulatory compliance throughout the software lifecycle. Regulatory definitions and organizational compliance rules are normalized into machine-interpretable representations and correlated with software build artifacts, configuration parameters, dependency relationships, and runtime telemetry associated with software deployment events. Machine learning-based compliance reasoning is applied to determine compliance states and associated confidence values, which are used to autonomously authorize, restrict, delay, or terminate deployment actions in real time. The system further incorporates adaptive learning mechanisms that refine compliance inference parameters based on historical outcomes and regulatory updates, as well as secure audit logging for traceability and verification.

A method for implementing a multi-party software build process using confidential computing includes encrypting, using one or more secret keys, a disk image of software configured to implement the software build process, storing the one or more secret keys and a key release policy that defines one or more conditions for releasing the one or more secret keys to entities associated with the software build process, and, using hardware configured to support operation of a trusted execution environment (TEE), launching a software environment within the TEE and performing a cryptographic measurement of the software environment, selectively providing the one or more secret keys based on validation of the cryptographic measurement of the software environment and the key release policy, and, using the one or more secret keys for decrypting the disk image, verifying integrity of the disk image, and launching the software build process.

Modifications to existing computer hardware, compiler changes or source-to-source transforms performed during the software build process, and a collection of libraries and modifications to existing standard system software and libraries. The invention allows a program author to enforce various kinds of locality of causality in software to provide enforcement of boundaries for the following aspects of a computer program: control, space, time, modularity, reference, initialization, and mutability. Where these properties do not suffice to guarantee a property at static time, dynamic checks may be added and the constraints on control flow prevent such dynamic checks from being avoided by the program.

This invention discloses a conditional compilation and dynamic feature management system, belonging to the field of software build and configuration management technology. The system includes a build-time conditional import module configured to selectively import modules using conditional expressions. These conditional expressions are evaluated during the build phase, and the module packaging tool completely removes module dependencies corresponding to inactive code branches during the build process. The system also includes a runtime feature checking module and a hierarchical feature control module, distinguishing between build-time feature control and runtime feature control. Build-time feature control achieves code elimination through conditional expressions, while runtime feature control dynamically controls the execution path through status query callbacks. The system further includes an on-demand loading module for delayed initialization of heavy subsystems; a code elimination verification module to verify the complete elimination of inactive code; a feature dependency management module to manage dependencies and mutual exclusion relationships between feature flags; a feature documentation generation module to automatically generate feature configuration documents; and a feature flag definition module to centrally define feature flags to ensure type safety. This invention achieves collaborative work between compile-time code optimization and runtime behavior control, balancing streamlined build artifacts with runtime flexibility, and can be widely applied to feature management and build optimization of large-scale software systems.

The disclosed system and process involve correlating outbound traffic with a CI / CD pipeline. CI / CD Pipelines consist of multiple jobs, and each job's steps execute on the same runner host. Network monitors relay information about domain names and network connections during job execution to the data store. Once all pipeline jobs are complete, the correlation server links domain names and connections to determine endpoints. This correlation, showing outbound traffic for each step, is accessible to the pipeline owner for review. An alert is triggered for new endpoints relative to the baseline. Owners can block unexpected endpoints based on explicitly defined lists. The correlation server also identifies file events, aiding in detecting suspicious file and software build overwrite events for combating software supply chain attacks. Observed file and network events contribute to generating a Software Bill of Materials (SBOM) through runtime events.