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.
Python utilities to interact with Darshan <https://www.mcs.anl.gov/research/projects/darshan/>
__
log records of HPC applications.
For examples and Jupyter notebooks to get started with PyDarshan make sure
to check out the examples
subdirectory.
To install in most cases the following will work::
pip install darshan
Targets for various tests are included in the makefile. To run the normal test suite use::
make test
Or to test against a different version of Python using Tox::
make test-all
Coverage tests can be performed using::
make coverage
Conformance to PEPs can be tested using flake8 via::
make lint
Documentation for the Python bindings is generated separately from the darshan-util C library in the interest of using Sphinx. After installing the development requirements the documentation can be built using make as follows::
pip install -r requirements_dev.txt
make docs
FAQs
Python tools to interact with Darshan log records of HPC applications.
We found that darshan demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 2 open source maintainers 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.