Older releaseCurrent release 2.4.2
openssl
‹2.3.0
- 2.4.29 Jun 2026, current
- 2.4.114 May 2026
- 2.4.015 Apr 2026
- 2.3.526 Feb 2026
- 2.3.430 Sep 2025
- 2.3.326 May 2025
- 2.3.23 Feb 2025
- 2.3.19 Jan 2025
- 2.3.016 Dec 2024
- 2.2.220 Sep 2024
- 2.2.116 Aug 2024
- 2.2.016 May 2024
- 2.1.221 Apr 2024
- 2.1.125 Sep 2023
- 2.1.015 Jul 2023
- 2.0.610 Mar 2023
- 2.0.56 Dec 2022
- 2.0.417 Oct 2022
- 2.0.314 Sep 2022
- 2.0.224 May 2022
- 2.0.114 May 2022
- 2.0.02 Mar 2022
- 1.4.619 Dec 2021
- 1.4.52 Sep 2021
- 1.4.430 Apr 2021
- 1.4.318 Sep 2020
- 1.4.227 Jun 2020
- 1.4.118 Jul 2019
- 1.431 May 2019
- 1.322 Mar 2019
- 1.2.21 Mar 2019
- 1.2.117 Jan 2019
- 1.217 Jan 2019
- 1.115 Nov 2018
- 1.0.230 Jul 2018
- 1.0.13 Mar 2018
- 1.02 Feb 2018
- 0.9.910 Nov 2017
- 0.9.83 Nov 2017
- 0.9.76 Sep 2017
- 0.9.631 Dec 2016
- 0.9.528 Oct 2016
- 0.9.425 May 2016
- 0.9.34 May 2016
- 0.9.226 Feb 2016
- 0.9.118 Jan 2016
- 0.913 Jan 2016
- 0.815 Dec 2015
- 0.618 Nov 2015
- 0.515 Nov 2015
- 0.411 May 2015
- 0.37 Jan 2015
- 0.27 Nov 2014
- 0.121 Oct 2014
- Released
- 16 Dec 2024R 4.4.2 at the time
- 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 knownfor this release
- Test coverage, method
Method
Test coverage
Test coverage is measured by downloading each CRAN package's current source file, installing its dependencies, building it and running its tests under covr.
- Almost half of CRAN has no tests to run
- Only CRAN packages are measured. Many have no percentage, most often because the package has no tests, and that blank is a recorded outcome, not missing data.
- NOT_CRAN
- Tests run with NOT_CRAN=true, so tests that skip themselves on CRAN run here, and the figure can differ from what CRAN's own checks see.
- Current version only
- Only the current version is measured, and a new version on CRAN is measured again. Older rows are kept but never filled in later. This is one package's run.
- Never 0%
- On a package page three states stay apart: measured, no tests, and not measured. Neither of the last two is ever shown as 0%.
- –not measured for this release
- Public exports, method
Method
Code metrics
Code metrics come from reading the released source of each package version. The package is never installed, loaded or run.
- One row a version
- Each analysed version gives one row of figures. The Code, Tests and Documentation sections, the pages of older releases and Release changes all read from those rows.
- CRAN
- CRAN versions are read from the github.com/cran mirror, which holds one commit for each released source file, and every version tag is analysed. Nothing is built, installed or run.
- Release, not repository
- Documentation describes what the analysed release holds: a
README, vignettes, aNEWSfile 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. - Zero
- Zero means the analysis looked and found none.
- 78none added or removed
Record made 29 Oct 2026, 03:58 UTC from data release v2026-10-28, merged 23:10 UTC. Project DOI 10.5281/zenodo.21843040.
https:/
This page reports what R Observatory measured for this release. It is not a validation, and it does not say whether the package is fit for your intended use.
Compare
Compared with 2.4.2, released 9 Jun 2026.
- Time between
- 540 days7 releases in between
- Advisories
- None knownfor either release
- Exports
- 1 addednone removed
- Files changed
- 50+891 −772 lines
Values that differ (7)
| Measure | Section | 2.3.0 | 2.4.2 |
|---|---|---|---|
| Download size | Release | 1.2 MB | 1.1 MB |
| Public exports | Code | 78 | 79 |
| Lines of R code | Code | 2,743 | 2,766 |
| Lines of compiled code | Code | 3,760, 37.6% of code | 3,801, 37.6% of code |
| Tests | Tests | Yes, testthat (edition not declared, 2nd by default), 106 test blocks | Yes, testthat (edition not declared, 2nd by default), 107 test blocks |
| Exports named in tests | Tests | 71.8% | 74.7% |
| NEWS | Documentation | Yes, mentions 2.3.0 | Yes, mentions 2.4.2 |
Exports added (1)
rsa_sign
Most changed files (12 of 50)
| File | Lines added | Lines deleted |
|---|---|---|
inst/doc/keys.html | 193 | 193 |
inst/doc/bignum.html | 129 | 129 |
MD5 | 107 | 107 |
inst/doc/secure_rng.html | 73 | 73 |
inst/doc/crypto_hashing.html | 28 | 28 |
DESCRIPTION | 26 | 26 |
src/cert.c | 24 | 23 |
src/openssh.c | 18 | 18 |
src/rsa.c | 31 | 4 |
src/stream.c | 17 | 17 |
NEWS | 26 | 0 |
src/hash.c | 12 | 12 |
Release
- Published
- 16 Dec 2024
- Status
- Replaced by 2.3.1 on 9 Jan 2025
- Previous
- 2.2.2, 20 Sep 2024
- License
- MIT + file LICENSE, OSI approved
- Maintainer
- Jeroen Ooms
- Download size
- 1.2 MB
- Authors
- Jeroen Ooms, Oliver Keyes
- Source code
- https://jeroen.r-universe.dev/openssl
Advisories
- This release
- None known
CRAN checks
Method, CRAN checks 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.
- Results
- Kept only for the current release
Code
- Lines of R code
- 2,743
- Public exports
- 78
- Internal functions
- 142
- Mean complexity
- 1.8the most is 15
Lines by kind (10,010)
| Kind | Lines | Share |
|---|---|---|
| R code | 2,743 | 27% |
| Tests | 2,023 | 20% |
| Documentation | 1,154 | 12% |
| Guides | 330 | 3% |
| Compiled code | 3,760 | 38% |
Tests
- Test cases
- 106
- Lines of tests
- 2,023
- Exports named in tests
- 71.8%
- Tests
- Yes, testthat (edition not declared, 2nd by default), 106 test blocks
- Test lines per line of code
- 0.74
- Coverage
- Not measured for this release
- Help pages with running examples
- 13 of 17
Documentation
- Exports documented
- 100%
- Arguments documented
- 100%
- Return value documented
- 4.5%
- Vignettes
- 4
- Help pages
- 23
- Exports with examples
- 77.3%
- NEWS
- Yes, mentions 2.3.0
- Citation file
- No
- Website
- Yes
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.
- Depends
- None
- Imports
- askpass
- LinkingTo
- None
- Suggests
- curl, testthat (>= 2.1.0), digest, knitr, rmarkdown, jsonlite, jose, sodium
- Install tree
- Kept only for the current release
- Advisories in the install tree
- Kept only for the current release
Today
Checks, downloads, dependents, people and the repository describe the package as it is now, so they are on the current release.
Sources
| Part | From | As of |
|---|---|---|
| Release history | CRAN package versions | 28 Oct 2026 |
| Advisories | osv-advisories 1.0.0, R version 4.6.1 (2026-06-24) | 28 Oct 2026 |
| CRAN checks | CRAN check results | Kept only for the current release |
| Tests, documentation, code | rpkg-analyzer 0.5.2 | 5 Oct 2026 |
| Coverage | covr | Not measured for this release |
| Use | CRAN downloads, reverse dependencies, repository | Not shown for this release |
Daily data releases are kept on GitHub, so the data behind this record can be fetched again from v2026-10-28 (merged 23:10 UTC). Values not kept for a release say so and are never filled in from another release.