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.
alidock
=======
Run your ALICE environment from a container. Install Docker,
then:
bash <(curl -fsSL https://raw.githubusercontent.com/alidock/alidock/master/alidock-installer.sh)
Windows users can install the package with pip instead.
You may need to close and reopen your terminal as advised. Run alidock now:
alidock
You are instantly dropped in a shell with a consistent ALICE environment from a Docker container.
From there you can directly run, for example:
aliBuild init O2@dev --defaults o2
aliBuild build O2 --defaults o2
and it will download the precompiled binaries for you.
Your home directory in the container, called /home/alidock
, is available from outside the
container in ~/alidock
. This means you can use your favourite text editor or IDE from your laptop,
no need to edit from inside the container.
📜 Full documentation available on the Wiki.
FAQs
Run your ALICE environment from a container easily
We found that alidock 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.