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.
The simplest way to serve AI/ML models in production
transformers
and diffusers
to PyTorch
and TensorFlow
to TensorRT
and Triton
, Truss supports models created and served with any framework.See Trusses for popular models including:
and dozens more examples.
Install Truss with:
pip install --upgrade truss
As a quick example, we'll package a text classification pipeline from the open-source transformers
package.
To get started, create a Truss with the following terminal command:
truss init text-classification
When prompted, give your Truss a name like Text classification
.
Then, navigate to the newly created directory:
cd text-classification
One of the two essential files in a Truss is model/model.py
. In this file, you write a Model
class: an interface between the ML model that you're packaging and the model server that you're running it on.
There are two member functions that you must implement in the Model
class:
load()
loads the model onto the model server. It runs exactly once when the model server is spun up or patched.predict()
handles model inference. It runs every time the model server is called.Here's the complete model/model.py
for the text classification model:
from transformers import pipeline
class Model:
def __init__(self, **kwargs):
self._model = None
def load(self):
self._model = pipeline("text-classification")
def predict(self, model_input):
return self._model(model_input)
The other essential file in a Truss is config.yaml
, which configures the model serving environment. For a complete list of the config options, see the config reference.
The pipeline model relies on Transformers and PyTorch. These dependencies must be specified in the Truss config.
In config.yaml
, find the line requirements
. Replace the empty list with:
requirements:
- torch==2.0.1
- transformers==4.30.0
No other configuration is needed.
Truss is maintained by Baseten, which provides infrastructure for running ML models in production. We'll use Baseten as the remote host for your model.
Other remotes are coming soon, starting with AWS SageMaker.
To set up the Baseten remote, you'll need a Baseten API key. If you don't have a Baseten account, no worries, just sign up for an account and you'll be issued plenty of free credits to get you started.
truss push
With your Baseten API key ready to paste when prompted, you can deploy your model:
truss push
You can monitor your model deployment from your model dashboard on Baseten.
After the model has finished deploying, you can invoke it from the terminal.
Invocation
truss predict -d '"Truss is awesome!"'
Response
[
{
"label": "POSITIVE",
"score": 0.999873161315918
}
]
Truss is backed by Baseten and built in collaboration with ML engineers worldwide. Special thanks to Stephan Auerhahn @ stability.ai and Daniel Sarfati @ Salad Technologies for their contributions.
We enthusiastically welcome contributions in accordance with our contributors' guide and code of conduct.
FAQs
A seamless bridge from model development to model delivery
We found that truss demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 6 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.