The hardware and bandwidth for this mirror is donated by METANET, the Webhosting and Full Service-Cloud Provider.
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[@]metanet.ch.
The {rosv} package is an API client to the Open Source Vulnerability (OSV) database. Both high and low level functions are available to query the database for vulnerabilities in package repositories across various open source ecosystems such as CRAN, Bioconductor, PyPI, and many more. Queries made against the OSV database are useful to check for package vulnerabilities (including by specific versions) enumerated in package management files such as requirements.txt
(Python) and renv.lock
(R). Checking valid query construction, API response pagination, and parsing content are all handled by {rosv}.
Various helper functions assist in the administration of Posit Package Manager or similar services. Packages can be routinely examined for new vulnerabilities which aide in the creation and updating of curated repositories as well as assigning block lists.
More details about the OSV project and associated API can be found here: https://google.github.io/osv.dev/.
For the latest development version, you can install {rosv} from GitHub:
The fastest and simplest way to get started with {rosv} is to use the osv_query()
function.
Provide a package name and related ecosystem to fetch any identified vulnerabilities.
Query multiple packages at the same time and across ecosystems.
Return results only for packages provided and not others that may be part of the same vulnerability.
Download all vulnerabilities listed for an ecosystem.
{rosv} leverages {httr2} and {httptest2} for its core API client functionality and uses R6 classes for its low-level interface to the OSV API. There are also plans to have more types of returned details and parsing of content.
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.