Microsoft Application Inspector is a software source code characterization tool that helps identify coding features of first or third party software components based on well-known library/API calls and is helpful in security and non-security use cases. It uses hundreds of rules and regex patterns to surface interesting characteristics of source code to aid in determining what the software is or what it does from what file operations it uses, encryption, shell operations, cloud API's, frameworks and more and has received industry attention as a new and valuable contribution to OSS on ZDNet, SecurityWeek , CSOOnline , Linux.com/news , HelpNetSecurity, Twitter and more and was first featured on Microsoft.com.
Application Inspector is different from traditional static analysis tools in that it doesn't attempt to identify "good" or "bad" patterns; it simply reports what it finds against a set of over 400 rule patterns for feature detection including features that impact security such as the use of cryptography and more. This can be extremely helpful in reducing the time needed to determine what Open Source or other components do by examining the source directly rather than trusting to limited documentation or recommendations.
Be sure to see our complete project wiki page https://Github.com/Microsoft/ApplicationInspector/wiki for additional information and help.
dotnet tool install --global Microsoft.CST.ApplicationInspector.CLI
See more in the wiki
appinspector analyze -s path/to/src.
applicationinspector.cli.exe analyze -s path/to/src
Microsoft Application Inspector helps you in securing your applications from start to deployment.
Design Choices - Enables you to choose which components meet your needs with a smaller footprint of unnecessary or unknowns features for keeping your application attack surface smaller as well as help to verify expected ones i.e. industry standard crypto only.
Identifying Feature Deltas - Detects changes between component versions which can be critical for detecting injection of backdoors.
Automating Security Compliance Checks - Use to identify components with features that require additional security scrutiny, approval or SDL compliance as part of your build pipeline or create a repository of metadata regarding all of your enterprise application.
We have a strong default starting base of Rules for feature detection. But there are many feature identification patterns yet to be defined and we invite you to submit ideas on what you want to see or take a crack at defining a few. This is a chance to literally impact the open source ecosystem helping provide a tool that everyone can use. See the Rules section of the wiki for more.
Application Inspector is in GENERAL AUDIENCE release status. Your feedback is important to us. If you're interested in contributing, please review the CONTRIBUTING.md.
Application Inspector is availble as a command line tool or NuGet package and is supported on Windows, Linux, or MacOS.
Platform specific binaries of the ApplicationInspector CLI are available on our GitHub releases page.
The C# library is available on NuGet as Microsoft.CST.ApplicationInspector.Commands .
The .NET Global Tool is available on NuGet as Microsoft.CST.ApplicationInspector.CLI.
> appinspector --help ApplicationInspector.CLI 1.4.0+6bdef0356b c Microsoft Corporation. All rights reserved. analyze Inspect source directory/file/compressed file (.tgz|zip) against defined characteristics tagdiff Compares unique tag values between two source paths exporttags Export unique rule tags to view what code features may be detected verifyrules Verify custom rules syntax is valid packrules Combine multiple rule files into one file for ease in distribution help Display more information on a specific command. version Display version information.
To get help for a specific command run
appinspector <command> --help.
The Analyze Command is the workhorse of Application Inspector.
This will produce an output.html of the analysis in the current directory using default arguments and rules.
appinspector analyze -s path/to/files
appinspector analyse -s path/to/files -f sarif -o output.sarif
This will create a json output named data.json of the analysis in the current directory, excluding all files in
.git folders using the provided glob patterns.
appinspector analyze -s path/to/files -o data.json -f json -g **/tests/**,**/.git/**
For additional help on use of the console interface see CLI Usage.
For help using the NuGet package see NuGet Support