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.
🚧 Under development 🚧
Server/client BERT fine tunning app using active learning
Python refactoring of R Shiny ActiveTigger app (Julien Boelaert & Etienne Ollion)
You can install activetigger
via pip (be careful to use Python 3.11):
pip install activetigger
Create a config file config.yaml
in the directory where you want to launch the server :
path
: path to store files (for instance ./data
)secret_key
: to secure tokens. To generate it openssl rand -hex 32C
path_models
: absolute path to fasttext modelsThen, to launch the server (on 0.0.0.0 port 8000 by default). You can configurate exposed port if needed.
python -m activetigger
Otherwise, you can launch only the API with uvicorn
:
uvicorn activetigger.api:app --host 0.0.0.0 --port 80 --reload
You can create/delete users with the root account.
You can also create a add_users.yaml
file with the users to add when the server starts :
user1: password1
user2: password2
FAQs
ActiveTigger in Python
We found that activetigger 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.