So for example, rOpenSci has http://packages.ropensci.org/ which is just a Jenkins landing page. But the UI does not really matter as it would be used inside R not from the browser. The main thing is that src/contrib returns a list of packages, that src/contrib/PACKAGES returns a file and that we have tar.gz files in src/contrib.
Example:
- http://packages.ropensci.org/src/contrib this would be re-generated on update of packages but would be a static page
- http://packages.ropensci.org/src/contrib/PACKAGES - same as above
- http://packages.ropensci.org/src/contrib/pdftools_2.3.1.9000.tar.gz - an example of a package
Rstan source package is 1 MB, its MacOS binary is ~20MB and its Windows binary I think ~5MB. And that package is probably among the largest we would host (rstanarm is a bit bigger but this is the general ballpark for largest packages) .
RStan has 85K downloads per month on CRAN, this would definitely much less than that. Would it handle lets says 1k per month or 10k?