Fast and accurate identification of message-based API calls in application binaries

1. A system, comprising:

at least one computing device; and

at least one service executable in the at least one computing device, the at least one service, when executed, causing the at least one computing device to at least:

obtain a set of compliance rules from a compliance rule store;

receive a request to analyze an application;

perform an application analysis by scanning the application to identify at least one public application programming interface (API) invoked by the application;

generate a developer reputation record based at least in part on the application analysis; and

enforce the set of compliance rules on the application based at least in part on the application analysis and the developer reputation record.

2. The system of claim 1 , wherein the at least one service, when executed, further causes the at least one computing device to at least, based at least in part on the application analysis, wrap the application or embed a software development kit (SDK) in the application.

3. The system of claim 1 , wherein the at least one service, in performing the application analysis, further causes the at least one computing device to:

obtain data identifying a plurality of public API definitions; and

determine the at least one public API invoked by the application by comparing a listing of external classes from the application and a listing of external methods from the application with the data identifying the plurality of public API definitions.

4. The system of claim 3 , wherein the at least one service, in performing the application analysis, further causes the at least one computing device to at least determine the listing of external classes and the listing of external methods based at least in part on analyzing binary code of the application and analyzing metadata of the application.

5. The system of claim 4 , wherein analyzing the binary code of the application produces a listing of local classes and a list of local methods, and analyzing the metadata of the application produces a listing of local and external classes and a listing of local and external methods.

6. A method, comprising:

obtaining a set of compliance rules from a compliance rule store;

receiving a request to analyze an application;

performing an application analysis by scanning the application to identify at least one public application programming interface (API) invoked by the application;

generating a developer reputation record based at least in part on the application analysis; and

enforcing the set of compliance rules on the application based at least in part on the application analysis and the developer reputation record.

7. The method of claim 6 , further comprising:

based at least in part on the application analysis, wrapping the application or embedding a software development kit (SDK) in the application.

8. The method of claim 6 , further comprising performing forward constant propagation to determine a plurality of instructions of the application that invoke the at least one public API.

9. The method of claim 6 , wherein performing the application analysis further comprises:

obtaining data identifying a plurality of public API definitions; and

determining the at least one public API invoked by the application by comparing a listing of external classes from the application and a listing of external methods from the application with the data identifying the plurality of public API definitions.

10. The method of claim 9 , further comprising determining the listing of external classes and the listing of external methods based at least in part on analyzing binary code of the application and analyzing metadata of the application.

11. The method of claim 10 , wherein analyzing the binary code of the application produces a listing of local classes and a list of local methods, and analyzing the metadata of the application produces a listing of local and external classes and a listing of local and external methods.

12. A non-transitory computer-readable medium embodying a program executable in at least one computing device, wherein when executed the program causes the at least one computing device to at least:

obtain a set of compliance rules from a compliance rule store;

receive a request to analyze an application;

perform an application analysis by scanning the application to identify at least one public application programming interface (API) invoked by the application;

generate a developer reputation record based at least in part on the application analysis; and

enforce the set of compliance rules on the application based at least in part on the application analysis and the developer reputation record.

13. The non-transitory computer-readable medium of claim 12 , wherein when executed the program causes the at least one computing device to at least wrap the application based at least in part on the application analysis.

14. The non-transitory computer-readable medium of claim 12 , wherein when executed the program causes the at least one computing device to at least embed a software development kit (SDK) in the application based at least in part on the application analysis.

15. The non-transitory computer-readable medium of claim 12 , wherein when executed the program causes the at least one computing device to at least perform forward constant propagation to determine a plurality of instructions of the application that invoke the at least one public API.

16. The non-transitory computer-readable medium of claim 12 , wherein performing the application analysis further comprises:

obtaining data identifying a plurality of public API definitions; and

determining the at least one public API invoked by the application by comparing a listing of external classes from the application and a listing of external methods from the application with the data identifying the plurality of public API definitions.