Security News
Research
Data Theft Repackaged: A Case Study in Malicious Wrapper Packages on npm
The Socket Research Team breaks down a malicious wrapper package that uses obfuscation to harvest credentials and exfiltrate sensitive data.
node-jasmine-phantomjs
Advanced tools
PhantomJS Runner for Jasmine 1.x
The jasmine-phantomjs module provides the jasmine-phantomjs.js
script and extensions to drive PhantomJS to enable testing your specs within a browser with Jasmine from the console. The preferred usage is to install mocha-phantomjs
via node's packaged modules and use the mocha-phantomjs
binary wrapper.
Jasmine is a feature-rich JavaScript test framework running on node and the browser. PhantomJS is a headless WebKit with a Javascript API. It has fast and native support for various web standards like DOM handling, CSS selectors, JSON, Canvas, and SVG.
This plugin was created with a significant amount of inspiration from mocha-phantomjs.
FAQs
PhantomJS Runner for Jasmine 1.x
The npm package node-jasmine-phantomjs receives a total of 2 weekly downloads. As such, node-jasmine-phantomjs popularity was classified as not popular.
We found that node-jasmine-phantomjs 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.