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.
A JavaScript library of spatial predicates and functions for processing geometry
This version of JSTS is refactored to ES6 for the sole purpose of importing it to TurfJS.
More information about the original library: https://github.com/bjornharrtell/jsts
This library is not intended to be used outside of TurfJS
JSTS
JSTS has big problems when making it ES Module & CJS compatible.
The other major issue I found was the extend()
method that JSTS uses copies the entire section of that source code. For example if we have 4 Turf modules that use JSTS, that means we will have 4x GeoJSONReader source code in the final Rollup bundle.
Refactoring JSTS to proper ES6 Classes which will allow Rollup and other bundling libraries to properly conduct Tree Shaking.
FAQs
A JavaScript library of spatial predicates and functions for processing geometry
The npm package turf-jsts receives a total of 482,571 weekly downloads. As such, turf-jsts popularity was classified as popular.
We found that turf-jsts 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.