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.
Scikit-Learn compatible wrappers for Keras Models.
SciKeras is derived from and API compatible with the now deprecated / removed tf.keras.wrappers.scikit_learn
.
An overview of the differences as compared to the TF wrappers can be found in our migration guide.
This package is available on PyPi:
# Tensorflow
pip install scikeras[tensorflow]
Note that pip install scikeras[tensorflow]
is basically equivalent to pip install scikeras tensorflow
and is offered just for convenience. You can also install just SciKeras with
pip install scikeras
, but you will need a version of tensorflow installed at
runtime or SciKeras will throw an error when you try to import it.
The current version of SciKeras depends on scikit-learn>=1.4.1post1
and Keras>=3.2.0
.
keras.wrappers.scikit_learn
Please see the migration section of our documentation.
Documentation is available at https://www.adriangb.com/scikeras/.
See CONTRIBUTING.md
FAQs
Scikit-Learn API wrapper for Keras.
We found that scikeras demonstrated a healthy version release cadence and project activity because the last version was released less than 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.