has-binary2
Advanced tools
A function that takes anything in javascript and returns true if its argument contains binary data.
The has-binary2 npm package is used to check whether an object contains any binary data (in the form of ArrayBuffer, Blob, File, or other types). It is commonly used in applications that need to handle different types of data and specifically identify binary data, such as when working with WebSockets or other real-time communication protocols.
Detecting binary data in objects
This feature allows you to check if an object contains binary data. The function returns true if any binary data is found within the object.
const hasBinary = require('has-binary2');
const obj = { hello: 'world', image: new Buffer('binarydata') };
const containsBinary = hasBinary(obj); // returns trueThis package is similar to has-binary2 in that it is used to determine if a file contains binary data. However, isbinaryfile specifically works with file paths or file contents, rather than arbitrary objects.
Simple module to test if an object contains binary data
FAQs
A function that takes anything in javascript and returns true if its argument contains binary data.
We found that has-binary2 demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
Research
The Socket Research Team breaks down a malicious wrapper package that uses obfuscation to harvest credentials and exfiltrate sensitive data.
Research
Security News
Attackers used a malicious npm package typosquatting a popular ESLint plugin to steal sensitive data, execute commands, and exploit developer systems.
Security News
The Ultralytics' PyPI Package was compromised four times in one weekend through GitHub Actions cache poisoning and failure to rotate previously compromised API tokens.