Compare packages
Choose two to five packages from CRAN or Bioconductor.
- mlr3torch0.3.3CRAN
Add one more package to compare it with.
Declared
Method, Declared Method Licence figures come from the Licences
License field of each package's DESCRIPTION file, read the way R itself reads it. No licence file is opened.tools::analyze_license() and R's own licence database, as CRAN's checks read it.| is read, so one string can offer two families.
| Field | mlr3torch |
|---|---|
| Title | Deep Learning with 'mlr3' |
| Licence | LGPL (>= 3) |
| As R reads it | LGPL-3.0-only, OSI approved |
| Needs R | >= 3.5.0 |
| Compiled code | No |
| System requirements | None |
OSI approval comes from R's licence database and the ids from SPDX. No licence here is judged against another.
Health
Method, Health Method CRAN runs every current package through Checks and health
R CMD check on a set of machines and publishes a result for each one. The health shown on a package page comes from these results alone.
| Check | mlr3torch |
|---|---|
| CRAN checks | 13 OK |
| CRAN deadline | None |
| Dependencies with a CRAN deadline | 0 |
| Advisories on the current release | None known |
Downloads
Method, Downloads Method Download figures count requests logged by each distribution channel. They are not counts of installs or of users, because each channel publishes its own totals and this site reads them.Downloads
- mlr3torch2,996CRAN mirror, last 30 days
Dependencies
Method, Dependencies Method Dependent packages are other packages that list this one under Reverse dependencies
Depends, Imports or LinkingTo in their DESCRIPTION file. Those fields list the packages a package needs to install, so dependents break if this one is archived or broken.Suggests install and run without it, and use it for tests, examples or an optional feature. They are counted as Suggested by, never among the dependents, and a package that also lists it under one of the three fields is a dependent and is not counted again.
| Names | mlr3torch |
|---|---|
| Needs, beyond R | 12 backports, checkmate, cli, data.table, lgr, mlr3, mlr3misc, mlr3pipelines, paradox, R6, torch, withr |
| Comes with R | 1 methods |
| Installs with it | 46 backports, bit, bit64, callr, checkmate, cli, coro, data.table, desc, digest, evaluate, farver and 34 more |
| Suggests or enhances | 17 callr, curl, future, ggplot2, igraph, jsonlite, knitr, mlr3tuning, progress, rmarkdown, testthat, tfevents and 5 more |
| Figure | mlr3torch |
|---|---|
| Dependent CRAN packages | 1 |
| Through other packages | 1 |
| Suggested by CRAN packages | 3 |
| Installs with it, to compile | 21 |
| Installs with it, compressed source | 26.1 MB |
Code
Method, Code Method Code metrics come from reading the released source of each package version. The package is never installed, loaded or run.Code metrics
README, vignettes, a NEWS file and the shares read from its help pages. Files kept only in the repository, such as a pkgdown configuration or CI files, are read by the repository scan instead.
| Figure | mlr3torch |
|---|---|
| Lines of R code | 14,148 |
| Lines of compiled code | 0 |
| Public exports | 157 |
| Internal functions | 181 |
| Names | mlr3torch |
|---|---|
| Exported functions it defines | 41 ModelDescriptor, TorchIngressToken, as_data_descriptor, as_lazy_tensor, as_lr_scheduler, as_torch_callback, as_torch_callbacks, as_torch_loss, as_torch_optimizer, assert_lazy_tensor, auto_device, batchgetter_categ and 29 more |
Functions it re-exports from another package are left out.
Tests
Method, Tests Method Test coverage is measured by downloading each CRAN package's current source file, installing its dependencies, building it and running its tests under covr.Test coverage
| Figure | mlr3torch |
|---|---|
| Lines run by tests | 0% |
| Test cases | 648 |
| Test lines per line of code | 0.69 |
| Exports named in tests | 80.9% |
Documentation
| Figure | mlr3torch |
|---|---|
| Exports documented | 100% |
| Arguments documented | 97.2% |
| Examples run in checks | 100% |
| Guides | 0 |
| README and NEWS | Both |
People
Method, People Method People on the site are the names packages give them in their Author and maintainer identity
DESCRIPTION files: authors from the author list, and the maintainer from the Maintainer field. Spellings of one name become one person only where the rules below allow it, and when in doubt the rules keep people apart.
Repository
Method, Repository Method Repository signals are the figures read from the source repository a package links to: stars, forks, issues, commits, releases and the time issues take to close. They are read from GitHub, GitLab, Codeberg and Bitbucket.Repository signals
URL and BugReports fields of its DESCRIPTION file. Read-only mirrors, the cran and bioc accounts on GitHub and git.bioconductor.org, are left out.
| Field | mlr3torch |
|---|---|
| Website | mlr3torch.mlr-org.com |
| Repository | github.com/mlr-org/mlr3torch |
| Issues | github.com/mlr-org/mlr3torch/issues |
| Stars | 56 |
| Forks | 10 |
| Open issues | 8 |
| Last commit | 22 Oct 2026 |
| Created | 12 Oct 2021 |
History
Method, History Method Archived is built from CRAN's archive records, its list of check deadlines and Bioconductor's package records. Every figure is counted to 28 Oct 2026, the day the data was read.Packages leaving
| Figure | mlr3torch |
|---|---|
| Status | On CRAN |
| First release | 8 Jul 2024 |
| Latest release | 31 Jan 2026 |
| Releases on record | 9 |
| Releases in the last 365 days | 2 |
| Median days between releases | 66 |
| Times CRAN archived it | 0 |