Iterator over the Control Flow Guard functions referenced by guard_cf_function_table()

Iterator over the Control Flow Guard functions referenced by [`LoadConfiguration::guard_cf_function_table`]

Iterator over the Guard EH continuation functions referenced by [`LoadConfiguration::guard_eh_continuation_table`]

List of RVA pointed by guard_address_taken_iat_entry_table()

Iterator over the functions referenced by [`LoadConfiguration::guard_long_jump_target_table`]

Unique identifier of the PDB file

The GUID signature to verify against the .pdb file signature. This attribute might be used to lookup remote PDB file on a symbol server.

The RVA of the module handle (in the ``.data`` section) It is used for storage by the routine that is supplied to manage delay-loading.

Check if the current segment has the given flag

Check if the function has the given flag

Check if the given DLL_CHARACTERISTICS is included in the dll_characteristics

Check if the given FILE_FLAGS is present

Whether the entry has the given flag

Check if this item has the given WINDOW_STYLES

Check if the given CHARACTERISTICS is used

Check if the given flag is used

Check if the given flag is present

`true` if the resources contain accelerator info

`true` if the binary has the command LC_ATOM_INFO.

Whether the current SymbolVersion has an auxiliary one

True if the symbol is associated with a BindingInfo This value is set when the symbol comes from the Dyld symbol bindings

`true` if the binary has the BuildVersion command.

`true` if the binary is signed with `LC_CODE_SIGNATURE` command

`true` if the binary is signed with the command `DYLIB_CODE_SIGN_DRS`

Check if the current binary has a load configuration

True if there is a data directory associated with this entry

`true` if the binary has a MachO::DataInCode command.

Check if the current binary contains debug information

`True` if the binary delay-imports the given library name

Check if the current binary contains delay imports

`true` if resources contain dialogs

`true` if the binary has the command LC_DYLD_CHAINED_FIXUPS.

`true` if the binary has Dyld envrionment variables.

`true` if the binary has the command LC_DYLD_CHAINED_FIXUPS.

`true` if the binary has a MachO::DyldInfo command.

`true` if the binary has a MachO::DylinkerCommand.

Check if the symbol with the given ``name`` exists in the dynamic symbols table

`true` if the binary has a MachO::DynamicSymbolCommand command.

`true` if the binary has Encryption Info.

`true` if the binary has an entrypoint. Basically for libraries it will return `false`

Check if the current binary has exceptions

True if the symbol is associated with an ExportInfo This value is set when the symbol comes from the Dyld Export trie

Check if the current binary has exports. @see Export

Whether there is a large number of relocations whose number need to be stored in the virtual address attribute

`true` if the binary has a LoadCommand::TYPE::FILESET_ENTRY command

`true` if the binary has a MachO::FunctionStarts command.

`true` if the binary has the command `LC_FUNCTION_VARIANT_FIXUPS`.

`true` if the binary has the command `LC_FUNCTION_VARIANTS`.

`true` if the resources contain html

`true` if resources contain a LIEF::PE::ResourceIcon

`True` if the binary imports the given library name

Check if the given library name exists in the current binary

Check if a MachO::DylibCommand is tied with the BindingInfo

`true` if the binary has the command LC_LINKER_OPTIMIZATION_HINT.

`true` if resources contain the Manifest element

`True` if the entry uses a name as ID

True if the binary contains `LC_NOTE` command(s)

Check if the binary uses `NX` protection

Check if the binary uses ``NX`` protection

Whether the binary defines a non-executable stack

Return True if the **heap** is flagged as non-executable. False otherwise

True if data are present at the end of the binary

Check if the current binary has relocations @see Relocation

Check if the current binary has resources

Check if the current binary has a RichHeader object