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.
ClassyConfig is a Python3 package aiming to remove the need for a config.py or settings.py file.
ClassyConfig is avliable via Pypi, so it can be installed using pip
$ pip install classy_config
from classy_config import ConfigValue, register_config
from pydantic import BaseModel
# Register your config file to be used
register_config(filepath="config.toml")
# Resolve default values based on your config
def print_current_version(version: str = ConfigValue("package", str)) -> None:
print(version)
# Use Pydantic Models for your config
class Author(BaseModel):
username: str
email: str
lucky_number: int
# Resolve default values based on your config
def print_author(author: Author = ConfigValue("author", Author)) -> None:
print(author)
# Allows for nested values
def print_value(value: int = ConfigValue("nested.value", int)) -> None:
print(value)
FAQs
ClassyConfig is a Python3 package aiming to remove the need for a config.py or settings.py file.
We found that classy-config 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.