ramlegacy
0.2.0CRANDownload and Read RAM Legacy Stock Assessment Database
Archived on 12 Jun 2025
- CRAN's reason
issues were not corrected despite reminders
Checks not fixed- Last release
- 0.2.0, 16 May 2019
# Needs the pak package.
# install.packages("pak")
pak::pak("cran::ramlegacy@0.2.0") - CRAN checks, method
Method
Checks and health
CRAN runs every current package through
R CMD checkon a set of machines and publishes a result for each one. The health shown on a package page comes from these results alone.- Problems
- Notes alone never count against a package, but a warning, an error or a failure on any platform is a problem. Open CRAN deadlines are a fact of their own, shown as a clock after the mark, so the mark always says what the checks found.
- Checks only
- Health reflects CRAN's check results and nothing else. Even a package with no tests, no coverage or no recent release can have every platform OK.
- Once a day
- Results are collected once a day from files CRAN publishes. Each platform is one machine set-up, named by its R version, operating system, architecture and compiler, such as r-devel-linux-x86_64-fedora-clang.
- Platforms counted
- The 13 in 3 of 13 is the number of platform rows CRAN published for that package on the day of collection. The set of machines changes over time, so the number is not fixed, and a package missing from a platform counts as neither passing nor failing there.
- Not checkedarchived 12 Jun 2025
- Dependent packages, method
Method
Reverse dependencies
Dependent packages are other packages that list this one under
Depends,ImportsorLinkingToin theirDESCRIPTIONfile. Those fields list the packages a package needs to install, so dependents break if this one is archived or broken.- As declared
- The counts follow the declarations as written, not whether a package uses the other one when it runs.
- Suggests apart
- Packages that list this one only under
Suggestsinstall 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. - Zero
- Zero dependents means no current CRAN package declares a need for this one, though some may suggest it. On 28 Oct 2026, 19,572 of the 25,583 current CRAN packages had no dependent package.
- 0none suggest it
- Advisories, method
Method
Security advisories
Advisories come from the R Consortium advisory database, a community record of security problems in R packages, as OSV publishes it.
- The copy
- The record is read once a day. The data is published under the Apache License 2.0 and is credited on the advisories list.
- Box under the name
- Under the package's name, a box names any advisory that affects the current release, with its fix or that there is none.
- Ranges
- Advisories state ranges, such as from 0.9.12 up to but not including 1.8.8. Each range is checked against every version CRAN has published, using the version rules R itself uses, so a release that came out after the advisory was written is still caught by its range.
- Not the package
- The rating is for the library flaw itself, not for how exposed the R package is, and it is never added up into a figure for the package.
- None known
About
Method, About 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.
Contains functions to download, cache and read in 'Excel' version of the RAM Legacy Stock Assessment Data Base, an online compilation of stock assessment results for commercially exploited marine populations from around the world. The database is named after Dr. Ransom A.
Full description
Contains functions to download, cache and read in 'Excel' version of the RAM Legacy Stock Assessment Data Base, an online compilation of stock assessment results for commercially exploited marine populations from around the world. The database is named after Dr. Ransom A. Myers whose original stock-recruitment database, is no longer being updated. More information about the database can be found at <https://ramlegacy.org/>. Ricard, D., Minto, C., Jensen, O.P. and Baum, J.K. (2012) <doi:10.1111/j.1467-2979.2011.00435.x>.
- Maintainer
- Kshitiz Gupta
- Licence
- MIT + file LICENSE
- Latest release
- 16 May 2019
- First release
- 16 May 2019
More details
- Releases
- 1
- Needs R
- >= 2.10
- Language
- en-CA
- LazyData
- true
- RoxygenNote
- 6.1.1
Cite
Package
Run in R for the authors' entry:
citation("ramlegacy")The package provides a citation file, so citation() returns the authors' own entry.
It points to 10.1111/j.1467-2979.2011.00435.x, 10.5281/zenodo.2542919, 10.5281/zenodo.2542927, 10.5281/zenodo.2542935.
R Observatory
For a number measured here: a download total, a coverage figure, an archival date.
Balamuta, J. J. (2026). R Observatory: Metrics for ramlegacy version 0.2.0 [Data set]. HJJB, LLC. Data release v2026-10-28. https://doi.org/10.5281/zenodo.21843040
About
From data release v2026-10-28, which the citation names so these numbers can be found later.
Health
CRAN checks only the packages on CRAN, and it archived this one on 12 Jun 2025.
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
- Total downloads in the last 30 days
- 7−66.7% down on the 30 days before, the worse directionIt is the sum of 2 channels: r2u and autoCRAN.
r2u rank
19,986 of 30,526
r2u
1 downloads in the last 30 days
- Rank
- 19,986 of 30,526
- Change
- −66.7% down on the 30 days before, the worse direction
It is in the total. Take it out
autoCRAN
6 downloads in the last 30 days
- Rank
- 8,234 of 29,212
- Change
- −66.7% down on the 30 days before, the worse direction
It is in the total. Take it out
The total is 7 downloads in the last 30 days. It is the sum of 2 channels: r2u and autoCRAN.
Over time
Dependencies
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.
- Functions
- 17
- Public exports
- 3
- Lines of R code
- 781
- Median complexity
- 3
Functions (17)
Size and composition
Lines by kind (1,712)
| Kind | Lines | Share |
|---|---|---|
| R code | 781 | 46% |
| Tests | 305 | 18% |
| Documentation | 366 | 21% |
| Guides | 260 | 15% |
Lines by language
| Language | Lines | Share |
|---|---|---|
| R | 1,086 | 63% |
| Rd | 366 | 21% |
| Vignettes | 260 | 15% |
Languages are counted from file extensions.
- Files
- 39
- R functions
- 17
- Object systems
- S3: 1 methods
Complexity
- Median
- 3
- Mean
- 3.82
- Highest
- 17
- Median lines per function
- 12
About complexity
Cyclomatic complexity counts the independent paths through a function: 1 is a straight line, higher is harder to test. R functions only.
Call graph figures
- R functions
- 17
- Calls
- 22
- Unconnected
- 2
- Groups
- 1
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
No coverage run is on record for this package.
- Test cases
- 23
- Lines of tests
- 305
- Exports named in tests
- 100%
- Has tests
- Yes
- Test frameworks
- testthat
- Test lines per line of code
- 0.39
Documentation
- Exports documented
- 100%
- Arguments documented
- 100%
- Return value documented
- 0%
- Help pages with examples
- 75%
- Examples run in checks
- 33.3%
Other documentation
- README
- Yes, 709 words
- Release notes file
- Yes
- Help pages
- 4
- Lines of documentation
- 366
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.
Maintainer since 0.2.0 (2019), author, copyright holder
Author, copyright holder
Reviewer
Reviewer
RAM Legacy Stock Assessment Database, an organisation
Data contributor
Repository
Method, figures by host 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.
No repository on record
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
- On CRAN
- Archived
- Release
Archived
| Archived | Back | CRAN's reason | Kind |
|---|---|---|---|
| 12 Jun 2025 | not back | issues were not corrected despite reminders | Checks not fixed |
| Version | Released | R | Events |
|---|---|---|---|
| 0.2.0 | 16 May 2019 | 3.6.0 | Archived 12 Jun 2025 “issues were not corrected despite reminders” |
Release notes (0.2.0)
- Removed the loading behavior of
library(ramlegacy)leaving the loading solely toload_ramlegacy - Instead of assigning all the tables to global environment
load_ramlegacynow just returns a list of tables that can be specified throughtablesargument. - Modified
download_ramlegacyandload_ramlegacyso that that while the default is still to download and read in the dataframes from the rappdirs directory the functions now also support downloading to a location chosen by the user and reading from that location.
For more fine-grained list of changes or to report a bug, consult
Versioning Guidelines
Releases will be numbered with the following semantic versioning format:
<major>.<minor>.<patch>
And constructed with the following guidelines:
- Breaking backward compatibility bumps the major (and resets the minor and patch)
- New additions without breaking backward compatibility bumps the minor (and resets the patch)
- Bug fixes and misc changes bumps the patch
- Following the RStudio convention, a .99 is appended after the patch number to indicate the development version on Github. Any version Coming from Github will now use the .99 extension, which will never appear in a version number for the package on CRAN.