The following is the corresponding gravitorch versions and supported dependencies.
gravitorch | 0.0.21 |
|---|---|
python | >=3.9,<3.12 |
coola | >=0.0.20,<0.0.23 |
hya | >=0.0.12,<0.0.14 |
hydra-core | >=1.3,<1.4 |
minevent | >=0.0.4,<0.0.5 |
numpy | >=1.22,<1.26 |
objectory | >=0.0.7,<0.0.8 |
pytorch-ignite | >=0.4.11,<0.5 |
tabulate | >=0.9,<0.10 |
torch | >=2.0,<2.1 |
colorlog* | >=6.7,<6.8 |
matplotlib* | >=3.6,<3.9 |
pillow* | >=9.0,<11.0 |
psutil* | >=5.9,<5.10 |
startorch* | >=0.0.5,<0.0.6 |
tensorboard* | >=2.10,<2.15 |
torchdata* | >=0.6,<0.7 |
tqdm* | >=4.64,<4.67 |
* indicates an optional dependency
:warning: While gravitorch is in development stage, no API is guaranteed to be stable from one
release to the next. In fact, it is very likely that the API will change multiple times before a
stable 1.0.0 release. In practice, this means that upgrading gravitorch to a new version will
possibly break any code that was using the old version of gravitorch.
gravitorch is licensed under BSD 3-Clause "New" or "Revised" license available
in LICENSE file.
FAQs
A library to train ML models with PyTorch
We found that gravitorch 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.
Research
The Socket Research Team investigates a malicious npm package that appears to be an Advcash integration but triggers a reverse shell during payment success, targeting servers handling transactions.
Security Fundamentals
The Socket Threat Research Team uncovers how threat actors weaponize shell techniques across npm, PyPI, and Go ecosystems to maintain persistence and exfiltrate data.
Security News
At VulnCon 2025, NIST scrapped its NVD consortium plans, admitted it can't keep up with CVEs, and outlined automation efforts amid a mounting backlog.
