2 services carry this tag in their source record. Tags come from the provider, not from us — a tag is a claim about what the service does, not proof that it does it well.
Executable header forensics for a file URL (defensive reverse-engineering): parses ELF (32/64, LE/BE), PE (32/64) and Mach-O headers — architecture, PIE/ASLR, NX stack, section entropy, imports, compiler/linker timestamp...
Static file triage for any file URL (defensive reverse-engineering): magic/format identification, MD5/SHA-1/SHA-256 hashes, Shannon entropy with packed-region detection, embedded-file signature scan and classified string...