The hardware and bandwidth for this mirror is donated by dogado GmbH, the Webhosting and Full Service-Cloud Provider. Check out our Wordpress Tutorial.
If you wish to report a bug, or if you are interested in having us mirror your free-software or open-source project, please feel free to contact us at mirror[@]dogado.de.
The goal of repo.data is to make repository data accessible. Mainly it consumes existing data but the idea is to also generate it.
When a function is specific of a repository it will start with its
name: cran_ or bioc_.
From CRAN:
install.packages("repo.data")You can install the development version of repo.data like so:
remotes::install_github("llrs/repo.data")We can get a data.frame of all packages on CRAN archive:
library(repo.data)
ca <- cran_archive()
#> Warning: There are 4 packages both archived and published
#> This indicate manual CRAN intervention.
head(ca)
#> Package Datetime Version User Size Status
#> 1 A3 2013-02-07 10:00:29 0.9.1 hornik 45252 archived
#> 2 A3 2013-03-26 19:58:40 0.9.2 ligges 45907 archived
#> 3 A3 2015-08-16 23:05:54 1.0.0 hornik 42810 archived
#> 4 AalenJohansen 2023-03-01 11:42:11 1.0 ligges 165057 current
#> 5 aamatch 2025-06-24 11:40:05 0.3.7 ligges 222104 current
#> 6 aaMI 2005-06-24 17:55:17 1.0-0 root 2968 archivedWe can also check CRAN comments about the packages on its archive:
cc <- cran_comments()
#> Retrieving comments, this might take a bit.
#> Caching results to be faster next call in this session.
head(cc)
#> package
#> 1 A3
#> 2 aaSEA
#> 3 aba
#> 4 abbyyR
#> 5 abcADM
#> 6 abcdeFBA
#> comment
#> 1 Archived on 2025-06-13 as issues were not corrected despite reminders.
#> 2 Archived on 2022-06-21 as check problems were not corrected despite reminders.
#> 3 Archived on 2022-03-27 as check problems were not corrected in time.
#> 4 Archived on 2023-11-03 at the maintainer's request.
#> 5 Archived on 2023-03-02 as issues were not corrected in time.
#> 6 Archived on 2022-03-07 as check problems were not corrected in time.
#> date action
#> 1 2025-06-13 archived
#> 2 2022-06-21 archived
#> 3 2022-03-27 archived
#> 4 2023-11-03 archived
#> 5 2023-03-02 archived
#> 6 2022-03-07 archivedOr estimate the last date of update of our packages, by the information on the session info or a data.frame:
cran_session(session = sessionInfo())
#> Warning in cran_archive(versions[, "Package"]): Omitting packages repo.data.
#> Maybe they were not on CRAN?
#> [1] "2025-08-27 18:40:06 CEST"
ip <- installed.packages()
cran_date(ip)
#> Warning in cran_archive(versions[, "Package"]): Omitting packages repo.data, AnnotationDbi, AnnotationFilter, AnnotationHub, BioCor, Biobase, BiocFileCache, BiocGenerics, BiocIO, BiocParallel, BiocPkgTools, BiocStyle, BiocVersion, Biostrings, DESeq2, DelayedArray, ExperimentHub, GO.db, GOSemSim, GSEABase, GenomeInfoDb, GenomeInfoDbData, GenomicAlignments, GenomicFeatures, GenomicRanges, HDF5Array, IRanges, KEGGREST, MatrixGenerics, ProtGenerics, Rhdf5lib, Rhtslib, Rsamtools, S4Arrays, S4Vectors, SingleCellExperiment, SparseArray, SummarizedExperiment, UCSC.utils, XVector, airway, alabaster.base, alabaster.matrix, alabaster.ranges, alabaster.sce, alabaster.schemas, alabaster.se, annotate, assorthead, biocViews, biomformat, cransays, ensembldb, fgsea, gypsum, h5mread, microshades, org.Hs.eg.db, phyloseq, preprocessCore, reactome.db, resios, rhdf5, rhdf5filters, rostemplate, rotemplate, rtracklayer, rutils, scRNAseq.
#> Maybe they were not on CRAN?
#> [1] "2025-08-29 16:00:06 CEST"Other packages and related analysis :
install.dates()
requires a CRAN date, if you are unsure you can use
cran_date() to estimate it given a library()
or a sessionInfo report.This package comes from the analysis on CRAN data on https://llrs.dev
These binaries (installable software) and packages are in development.
They may not be fully stable and should be used with caution. We make no claims about them.
Health stats visible at Monitor.