Install on environment. No configuration required.

Usage:

1. Create a File Inspector object, using Definitions packs according to your needs, including all acceptable/valid files types and/or extensions. Add custom file type(s) if necessary.

Definition packs make it easy to expand or limit the number of definitions that the Inspector will use.

2. Inspect a file using the previously created inspector object.

The inspection result can be a fully detailed result, or results grouped by file extension or file types.

Optimizing/Balancing Performance and Memory

• Trim the Data You Don't Need
  • Create definitions including only valid files.
  • Trim mime-types, file signatures and descriptions from responses.
• Slow Initialization = Fast Execution
  • Use the same inspector object when performing the same validation for multiple files.
• Parallel = True/False
  • The Parallel option controlls whether multiple threads will be used to perform detections. If you have lots of definitions or want to make optimal usage of your CPU, this should be set to true. If you have a low number of definitions or you want more balanced CPU usage, set this to false.