21 results about "Software artifacts" patented technology

A vehicle software bill of materials management service generates or updates a composite software bill of materials (composite SBOM) for a vehicle using one or more received software bill of materials (SBOMs). The vehicle software bill of materials management service allows a customer to define software artifact instances of the composite SBOM, including granularity of specificity and identity attributes. The vehicle software bill of materials management service maintains the composite SBOM and resolves conflict between different SBOMs. The vehicle software bill of materials management service resolves anomalies encountered during software artifact instance generation and enriches software artifact instances of the composite SBOM with additional metadata.

This invention specifically relates to a method for full lifecycle management and evaluation of enterprise information technology projects, belonging to the field of information technology project management technology. It includes: generating a software artifact knowledge graph based on software artifact information and its relationships contained in the four-dimensional quality evaluation index matrix, using requirement items, software architecture modules, code files, and test cases as entity nodes, and traceability and dependency relationships between entities as association edges. In this invention, a four-dimensional quality evaluation index matrix covering requirements, software architecture, code, and testing is established, expanding the project evaluation perspective from schedule and workload indicators to quality indicators within software engineering, enabling the quantitative identification of quality problems hidden beneath normal progress appearances.

Techniques for generating permissions policies for nested sets of software artifacts are disclosed. A system detects a selection of a target action and a target software artifact. The system identifies an entity associated with the selection. The system analyzes permissions metadata of the target software artifact to identify user-defined permission configuration rules specifying one or more additional software artifacts and one or more additional actions associated with the additional software artifacts. The system performs an iterative analysis of permissions metadata in the nested software artifacts to generate a composite permissions policy for the entity that combines the permissions specified in the user-defined permission configuration rules for the set of nested software artifacts.

A system for signing a software article is presented. The system comprises a software repository for storing one or more software products, a monitoring unit for monitoring the software repository, a software product creation unit designed to store new software products in the software repository, and a signature unit for signing the software products, wherein the monitoring unit is designed to monitor the software product creation unit (10) and, after a new software product is stored in the software store, to send an activation signal for signing the stored new software product to the signature unit, and wherein the signature unit is designed to sign the new software product in the software store. And signing the stored new software product based on the starting signal. As a result, it is possible to sign the software article after it is created and stored. This has the advantage that the signature can be integrated in a different, also already existing structure for creating a software article, since the signature is not executed during the creation process as in an existing system and thus does not need to be integrated in the creation process itself.

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.

Fingerprint inference of software artifacts includes receiving a request including classes, generating request fingerprints from the classes, and querying at least one index with the request fingerprints to identify a matching set of artifact versions. Fingerprint inference further includes obtaining, for each matching artifact version in the matching set of artifact versions, a count of the request fingerprints matching a indexed fingerprint related, in the at least one index, to the artifact version, and selecting a subset of the matching set of artifact versions having a count that is maximal amongst the matching set of artifact versions. Fingerprint inference further includes returning the subset of the matching set of artifact versions.

Techniques for generating permissions policies for nested sets of software artifacts are disclosed. A system detects a selection of a target action and a target software artifact. The system identifies an entity associated with the selection. The system analyzes permissions metadata of the target software artifact to identify user-defined permission configuration rules specifying one or more additional software artifacts and one or more additional actions associated with the additional software artifacts. The system performs an iterative analysis of permissions metadata in the nested software artifacts to generate a composite permissions policy for the entity that combines the permissions specified in the user-defined permission configuration rules for the set of nested software artifacts.

Quantitative quality assessments of a test automate generation tool can be performed automatically via an adapted mutation strategy. The test automate generation tool is employed to generate a corresponding test automate for each software artifact of a set of software artifacts. A domain expert manually creates mutated versions of the software artifacts. A set of mutant test automates is created programmatically for each test automate, where each mutant test automate in a given set corresponds to a given mutated version of the corresponding software artifact and is created by replacing references to the software artifact in the code of the test automate with references to the given one of the mutated versions of the software artifact. The test automates and mutant test automates are executed to obtain pass or fail test results, which are aggregated and output as a quantitative quality measure of the test automate generation tool.

This disclosure provides a model-driven software generation method, apparatus, electronic device, and storage medium, relating to the field of software development technology. It involves model file acquisition and execution environment cleanup, static detection of model specifications, automatic conversion of the model into source code, static scanning of code specifications, and code integration and compilation. The entire process, including the upload of detection results and the target software artifact to the cloud, terminates the process and generates a defect report if the detection fails. Therefore, it can solve the problems in existing technologies caused by non-standardized model development, non-standardized code generation and detection, lack of automated control over the development process, delayed defect discovery, lack of process sharing and traceability, and low team collaboration efficiency. It achieves the technical effects of fully automated development process, standardized models and code, early defect interception, traceable process, improved software quality and development efficiency, and reduced rework costs.

A system (100) for artificial intelligence (AI)-driven enterprise software modernization, the system (100) comprising: a. a user device (102) with a user interface (104) configured to receive legacy software artifacts including source code, configuration files, database schemas, interface definitions and runtime logs; b. a communication network (106) configured to enable data communication between the system's components and with external repositories and deployment environments; c. a processing unit (108) that is operationally connected to the user interface (104) of the user device (102) via the communication network (106), wherein the processing unit (108) is configured to execute an AI-driven software modernization workflow, the processing unit (108) comprising: i. a data input module (110) configured to receive legacy software artifacts via the user interface (104) and generate normalized artifact data; ii. a preprocessing module (112) configured to perform at least one of the syntactic analysis, dependency extraction, deobfuscation and metadata enrichment on the normalized artifact data; iii. a semantic intermediate representation generation module (114) configured to create a unified semantic representation that fuses static code semantics with behavioral information derived from runtime logs, the semantic intermediate representation comprising at least control flow structures, data flow relationships, API contracts, security constraints and performance attributes; iv. an artificial intelligence (AI) transformation module (118) configured to generate modernized software components based on the semantic intermediate representation; v. a validation module (120) configured to perform structural, behavioral and interface contract equivalence between the modernized software components obtained from the AI ​​transformation module (118) and the legacy software artifacts received via the data input module (110), and to transmit validation results to the AI ​​transformation module (118) for iterative correction; vi. an output module (122) configured to receive the validated modernized software components from the validation module (120) and to generate executable modernization artifacts, including source code, deployment descriptions and interface specifications, the artifacts being provided to the user device (102) via the communication interface (106).

Systems, computer program products, and methods for an automated mesh service-based deployment intelligence system are provided. This system is designed to streamline the deployment of software by integrating a processing device and a non-transitory storage device. The storage device contains instructions that, when executed by the processing device, enable the ingestion of data from various sources such as monitoring systems, databases, and application performance management tools. Once ingested, the data is stored and processed to discern deployment patterns and detect any anomalies. Utilizing a machine learning model, the system anticipates potential deployment issues by analyzing this data. It then orchestrates the deployment of software artifacts accordingly, taking into account the insights gained from the machine learning model. Furthermore, the system is capable of real-time optimization of the deployment process to preemptively resolve any predicted issues, thereby enhancing the efficiency and reliability of software deployment operations.

Systems and methods for a control plane to cryptographically trust and revoke the trust of anonymous software artifacts or devices are described. In an illustrative, non-limiting embodiment, an Information Handling System (IHS) may include: a processor; and a memory coupled to the processor, where the memory includes program instructions stored thereon that, upon execution by the processor, cause a control plane of the IHS to: receive an anonymous token of a distributed anonymous token set package from a requestor; verify the anonymous token; and subsequent to verifying the anonymous token, establish a trust relationship with the requestor.

The invention discloses a continuous integration method, device and system suitable for engineering machinery product software, and the method comprises the steps: selecting an adaptive assembly line template based on an obtained version change event, and generating an assembly line execution task; generating a software product based on the pipeline execution task; performing quality judgment on a construction log, a construction state and product data generated in a software product generation process based on the assembly line execution task, and determining to continue or stop executing the assembly line execution task according to a quality judgment result; performing automatic verification on the software product based on the assembly line execution task, and generating verification data; performing quality judgment on the verification data based on the assembly line execution task, and determining to continue or stop executing the assembly line execution task according to a quality judgment result; and performing unified archiving management on the software products passing the automatic verification. According to the method, automation and standardization of the whole process including code (model) submission, compiling construction (software product generation), test verification and product filing are achieved.

To provide a computer implemented method for verifying reliability of software deliverables, a software construction system, and a computer program product.SOLUTION: There is provided a computer implemented method for constructing reliable and executable software using reliable construction units between which a route is not reliable, the method including steps of: generating, for each reliable construction unit, an identifier for identifying an output of the reliable construction unit, the reliable construction unit also generating a confirmable certificate with a signature containing the identifier; utilizing, for each distributed reliable construction unit, at least one output result of a preceding construction unit among the reliable construction units as an input; verifying that each confirmable certificate with a signature conforms to a pre-determined series of policy rules; and terminating the construction of the reliable and executable software when the verification of one confirmable certificate with a signature among the reliable construction units has failed.SELECTED DRAWING: Figure 1

Embodiments describe techniques for validating the integrity and compliance of software artifacts through the use of attestations. An attestation manager is capable of retrieving an attestation file from storage, validating the software artifact and the attestation chain within the attestation, and optionally generate new attestations to add to the attestation chain when the software artifact and the attestation chain have been validated. A public-key encryption scheme may be applied to validate attestations while a fingerprint comparison scheme may be applied to validate the software artifact.

A system generates cryptographic receipts for lifecycle events associated with components and software artifacts. A canonical payload including an artifact digest and a policy identifier is authenticated using a key protected by a non-exportable key boundary. A digest derived from the canonical payload and authenticator is committed to a tamper-evident Merkle structure within an anchor window. An anchor artifact including at least a Merkle root hash and a monotonically increasing sequence value is produced for the anchor window. A receipt and a cryptographic proof of inclusion are provided to enable independent verification that a payload was recorded. A verification service validates the authenticator and inclusion proof, and controls promotion or enablement operations based on successful validation and policy requirements.

Techniques described herein relate to an extendable build system for generating software artifacts in multiple runtime environments. For example, a build system can receive a request from a client system to generate a software artifact in a particular runtime environment. The build system can include an interface that can enforce characteristics of the software artifact. The interface can be coupled to plugins that are each associated with a unique runtime environment. The build system can select a plugin associated with the particular runtime environment. The selected plugin can cause the software artifact that has the characteristics enforced by the interface to be generated in the particular runtime environment. The build system can receive access to the generated software artifact from the plugin and can provide the access to the client system in response to the request.

An example operation may include a method comprising one or more of constructing a VNF package that includes at least one of a VNFD with one or more VNFC module descriptors or one or more VNFC module artifacts, generating a VNF package archive, receiving the VNF package archive containing the VNF package, processing a manifest file in the VNF package archive, onboarding one or more traditional VNF package components including a VNFD file and at least one software artifact, onboarding one or more independently manageable VNFC software module components in the VNF package, and enabling a VNF in a service catalog.

The invention provides a software product difference analysis method, device and equipment, a medium and a program product, and relates to the field of financial science and technology or the field of big data. A difference analysis request of the software products is received, the difference analysis request comprises identifiers of a plurality of to-be-analyzed software products, and compressed packages of the plurality of software products are downloaded from a product warehouse based on the identifiers of the plurality of software products; respectively executing recursive decompression processing and decompilation processing on the compressed packages of the plurality of software products to obtain software file trees of the plurality of software products, and comparing the software file trees of the plurality of software products to obtain first difference information among the plurality of software products; according to the method, through automatic decompression, decompilation and file tree comparison, the fine-grained differences of the multiple software products on the file structure and code level are accurately recognized, and the efficiency and accuracy of difference analysis are improved.

A system and method for detecting a cybersecurity object in an operating system-level virtualization is presented. The method includes detecting an identifier of a code object in a software artifact, wherein the software artifact represents a software container deployed in a cloud computing environment; determining a location of the code object based on the software artifact; inspecting the code object for a cybersecurity object, wherein the cybersecurity object indicates a cybersecurity threat; detecting a cybersecurity object in the code object; and initiating a remediation action based on the cybersecurity object in response to detecting the cybersecurity object in the code object.

An example operation may include one or more of determining that a software artifact hosted by a pod within a cluster of a host platform contains code that is a security vulnerability, identifying a function within the software artifact that requests the code, activating a filter within the pod of the host platform which prevents execution of the function within the software artifact, and installing a fix for the security vulnerability within the software artifact.