Older releaseCurrent release 2.0.5
RJSONIO
‹1.3-1.8
- 2.0.515 May 2026, current
- 2.0.05 Apr 2025
- 1.3-1.1126 Mar 2025
- 1.3-1.1024 Mar 2025
- 1.3-1.927 Nov 2023
- 1.3-1.831 Jan 2023
- 1.3-1.714 Jan 2023
- 1.3-1.616 Sep 2021
- 1.3-1.517 Aug 2021
- 1.3-1.415 Jan 2020
- 1.3-1.33 Oct 2019
- 1.3-1.24 Jun 2019
- 1.3-1.13 Mar 2019
- 1.3-112 Nov 2018
- 1.3-028 Jul 2014
- 1.2-0.229 Apr 2014
- 1.2-0.126 Apr 2014
- 1.0-328 Mar 2013
- 1.0-220 Mar 2013
- 1.0-110 Oct 2012
- 1.0-030 Sep 2012
- 0.98-16 Feb 2012
- 0.98-02 Feb 2012
- 0.97-08 Jan 2012
- 0.96-023 Oct 2011
- 0.95-05 Sep 2011
- 0.94-023 Aug 2011
- 0.92-016 Aug 2011
- 0.91-015 Aug 2011
- 0.8-23 Aug 2011
- 0.8-130 Jul 2011
- 0.7-36 Jun 2011
- 0.7-210 May 2011
- 0.7-130 Apr 2011
- 0.5-022 Feb 2011
- 0.4-16 Dec 2010
- 0.3-14 Oct 2010
- Released
- 31 Jan 2023R 4.2.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.
- 11none added or removed
Record made 30 Oct 2026, 21:41 UTC from data release v2026-10-30, merged 18:36 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.0.5, released 15 May 2026.
- Time between
- 1,200 days4 releases in between
- Advisories
- None knownfor either release
- Exports
- No changebetween the two
- Files changed
- 86+11,240 −3,781 lines
Values that differ (12)
| Measure | Section | 1.3-1.8 | 2.0.5 |
|---|---|---|---|
| Maintainer | Release | CRAN Team | Yaoxiang Li |
| Download size | Release | 1.1 MB | 722 KB |
| Authors | Release | CRAN Team, Duncan Temple Lang, Jonathan Wallace | Yaoxiang Li, CRAN Team, Duncan Temple Lang, Jonathan Wallace |
| Lines of R code | Code | 867 | 887 |
| Lines of compiled code | Code | 13,372, 86.7% of code | 18,442, 85.5% of code |
| Complexity | Code | mean 5.7, highest 16 | mean 5.4, highest 16 |
| Tests | Tests | Yes, R scripts, 20 script files | Yes, testthat (3rd edition), 43 test blocks |
| Test lines per line of code | Tests | 0.47 | 0.92 |
| Exports named in tests | Tests | 45.5% | 72.7% |
| Vignettes | Documentation | 0 | 7 |
| NEWS | Documentation | No | Yes, mentions 2.0.5 |
| Suggests | Dependencies | None | knitr, rmarkdown, testthat (>= 3.0.0) |
Most changed files (12 of 86)
| File | Lines added | Lines deleted |
|---|---|---|
src/internalJSONNode.cpp | 828 | 0 |
inst/doc/overview.Rdb | 0 | 688 |
src/JSONWorker.cpp | 674 | 0 |
inst/doc/overview.tex | 0 | 605 |
src/libjson.cpp | 605 | 0 |
man/fromJSON.Rd | 301 | 299 |
inst/doc/overview.html | 0 | 535 |
inst/doc/Changes.html | 0 | 526 |
src/JSONPreparse.cpp | 499 | 0 |
inst/doc/parsing-json.html | 468 | 0 |
inst/doc/writing-json.html | 464 | 0 |
inst/doc/advanced-customization.html | 460 | 0 |
Release
- Published
- 31 Jan 2023
- Status
- Replaced by 1.3-1.9 on 27 Nov 2023
- Previous
- 1.3-1.7, 14 Jan 2023
- License
- BSD_3_clause + file LICENSE, OSI approved
- Maintainer
- CRAN Team
- Download size
- 1.1 MB
- Authors
- CRAN Team, Duncan Temple Lang, Jonathan Wallace
- Source code
- Not kept for this release
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
- 867
- Public exports
- 11
- Internal functions
- 0
- Mean complexity
- 5.7the most is 16
Lines by kind (15,420)
| Kind | Lines | Share |
|---|---|---|
| R code | 867 | 6% |
| Tests | 406 | 3% |
| Documentation | 775 | 5% |
| Compiled code | 13,372 | 87% |
Tests
- Test cases
- 0
- Lines of tests
- 406
- Exports named in tests
- 45.5%
- Tests
- Yes, R scripts, 20 script files
- Test lines per line of code
- 0.47
- Coverage
- Not measured for this release
- Help pages with running examples
- 5 of 6
Documentation
- Exports documented
- 100%
- Arguments documented
- 97.3%
- Return value documented
- 100%
- Vignettes
- 0
- Help pages
- 7
- Exports with examples
- 100%
- NEWS
- No
- Citation file
- No
- Website
- Not kept for this release
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
- methods
- LinkingTo
- None
- Suggests
- None
- 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 | 30 Oct 2026 |
| Advisories | osv-advisories 1.0.0, R version 4.6.2 (2026-10-29) | 30 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-30 (merged 18:36 UTC). Values not kept for a release say so and are never filled in from another release.