
Research
/Security News
Intercom’s npm Package Compromised in Ongoing Mini Shai-Hulud Worm Attack
Compromised intercom-client@7.0.4 npm package is tied to the ongoing Mini Shai-Hulud worm attack targeting developer and CI/CD secrets.
browserify-mockify
Advanced tools
Allows you to mock browserify modules for unit tests. If you transform your unit tests with browserify, you may need to mock certain modules (this helps with code coverage too).
npm install browserify-mockify
In your browserify task, add
var mockify = require('browserify-mockify');
var b = browserify();
b.transform(mockify.transform());
If you have any other transforms, pass each transform you use as arguments into mockify.transform. For example, if you were to use reactify -
b.transform(reactify);
b.transform(mockify.transform(reactify));
Using mockify.mock allows you to mock the modules you need. The first parameter should be the path relative to the module you are going to require (it should match the require path in the required module).
The second parameter can be whatever - this is what is returned instead of the actual module.
mockify.mock('./moduleB', {
hello: function () {
}
});
Replace any require calls that contains modules that you want to mock with mockify calls instead.
For example,
var module = require('./module');
Would become
var module = mockify('./module');
Your module.js file should look like
var moduleB = require('./moduleB');
When you run this normally in browserify, you will get moduleB returned. However, as you've defined a moduleB mock above, the object is returned when you run it in your tests.
FAQs
Mocks browserify modules for unit testing
We found that browserify-mockify 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.

Research
/Security News
Compromised intercom-client@7.0.4 npm package is tied to the ongoing Mini Shai-Hulud worm attack targeting developer and CI/CD secrets.

Research
Socket detected a malicious supply chain attack on PyPI package lightning versions 2.6.2 and 2.6.3, which execute credential-stealing malware on import.

Research
A brand-squatted TanStack npm package used postinstall scripts to steal .env files and exfiltrate developer secrets to an attacker-controlled endpoint.