An improved SDK includes a set of APIs and a crash handler registered with the operating system. Each API is an interface accessible by a computer software application. Up on entrance, each API determines the current thread identifier, and inserts it into a list if it is not already in the list. Each thread identifier corresponds to an API call counter, which is incremented by one at the entrance and decremented by one at the exit point of the API. The SDK also records the identifier of the thread it creates for callback functions. When a crash occurs, the crash handler is executed. It determines that the crash is related to a callback interface if the crash thread identifier matches the callback thread identifier. The crash is determined to be caused by the SDK if the API call counter corresponding to the crash thread identifier is greater than zero.

A technique manages objects in a software development project. In particular, in response to receiving a commit request for committing a group of objects, a group of historical commit requests associated with the group of objects are acquired based on a commit history, wherein historical commit requests in the group of historical commit requests involve the group of objects. A candidate object is selected from at least one object involved in the historical commit requests that is different from the group of objects. An association relationship between the candidate object and the group of objects is determined. The candidate object is identified as a missing object in response to determining that the association relationship satisfies a predetermined condition, the missing object indicating an object associated with the commit request but not included in the commit request. Accordingly, objects that are missing in a commit request can be automatically checked.

A technique manages objects in a software development project. In particular, in response to receiving a commit request for committing a group of objects, a group of historical commit requests associated with the group of objects are acquired based on a commit history, wherein historical commit requests in the group of historical commit requests involve the group of objects. A candidate object is selected from at least one object involved in the historical commit requests that is different from the group of objects. An association relationship between the candidate object and the group of objects is determined. The candidate object is identified as a missing object in response to determining that the association relationship satisfies a predetermined condition, the missing object indicating an object associated with the commit request but not included in the commit request. Accordingly, objects that are missing in a commit request can be automatically checked.

A serverless application center is provided for multi-cloud deployment of serverless applications. One method comprises providing source code, obtained from a first user acting in a developer role, for a multi-cloud serverless application in a serverless application repository; deploying, in response to a request from a second user acting in an end user role, source code for the multi-cloud serverless application from the serverless application repository to one or more clouds in plurality of distinct cloud environments based on the request; and implementing role-based access for users acting in said developer role and said end user role. A user interface can allow the second user to (i) review a published list of serverless applications available in the serverless application repository; and/or (ii) search a plurality of serverless applications available in the serverless application repository.

A serverless application center is provided for multi-cloud deployment of serverless applications. One method comprises providing source code, obtained from a first user acting in a developer role, for a multi-cloud serverless application in a serverless application repository; deploying, in response to a request from a second user acting in an end user role, source code for the multi-cloud serverless application from the serverless application repository to one or more clouds in plurality of distinct cloud environments based on the request; and implementing role-based access for users acting in said developer role and said end user role. A user interface can allow the second user to (i) review a published list of serverless applications available in the serverless application repository; and/or (ii) search a plurality of serverless applications available in the serverless application repository.

A method for analyzing performance impacts of changes to source code includes logging a change to source code and an identifier (ID) of an author of the change into a database. The method further includes providing the change to the source code to a machine learning model trained to analyze performance impacts of source-code changes. The method further includes generating, by a processing device, in view of the machine learning model, a performance impact of the change to the source code. The method further includes determining that the performance impact is above a performance-impact threshold. The method further includes, in view of the determining, preventing the change to the source code from being executed by the processing device.

A method for analyzing performance impacts of changes to source code includes logging a change to source code and an identifier (ID) of an author of the change into a database. The method further includes providing the change to the source code to a machine learning model trained to analyze performance impacts of source-code changes. The method further includes generating, by a processing device, in view of the machine learning model, a performance impact of the change to the source code. The method further includes determining that the performance impact is above a performance-impact threshold. The method further includes, in view of the determining, preventing the change to the source code from being executed by the processing device.

A system for enforcing compliance and testing for software development, comprising an indexing service configured to create a dataset by processing and indexing source code of a project by a developer, perform a code audit on the indexed source code, store results from the code audit in the dataset, gather additional information relating to the provided project, store the additional information in the dataset, and store the dataset into memory; and a monitoring service configured to continuously monitor the project for source code changes and make changes to the dataset as needed. Further comprising an enforcement module to automatically verify code and other media related to the software development process by ensuring obligations from a rules database are met and where not able to automate the compliance check forward to an appropriate authority, receive back the manually reviewed compliance check, then produce and implement automated recommendations for compliance adherence.

A system for enforcing compliance and testing for software development, comprising an indexing service configured to create a dataset by processing and indexing source code of a project by a developer, perform a code audit on the indexed source code, store results from the code audit in the dataset, gather additional information relating to the provided project, store the additional information in the dataset, and store the dataset into memory; and a monitoring service configured to continuously monitor the project for source code changes and make changes to the dataset as needed. Further comprising an enforcement module to automatically verify code and other media related to the software development process by ensuring obligations from a rules database are met and where not able to automate the compliance check forward to an appropriate authority, receive back the manually reviewed compliance check, then produce and implement automated recommendations for compliance adherence.

A system and method for meta-indexing, search, compliance, and test framework for software development using smart contracts is provided, comprising an indexing service configured to create a dataset by processing and indexing source code of a project provided by a developer, perform a code audit on the indexed source code, store results from the code audit in the dataset, gather additional information relating to the provided project, store the additional information in the dataset, and store the dataset into memory; and a monitoring service configured to continuously monitor the project for at least source code changes and make changes to the dataset as needed. Additionally, a smart contract authority creates and enforces smart contracts for every transaction taking place upon the software essentially mandating and guaranteeing the security and authenticity of the software during the software's development and use.