Older releaseCurrent release 2.1-24
R2WinBUGS
‹2.1-22.1
- 2.1-2423 Feb 2026, current
- 2.1-2323 Jul 2025
- 2.1-22.15 Feb 2024
- 2.1-2216 Dec 2023
- 2.1-2130 Jul 2015
- 2.1-2031 May 2015
- 2.1-197 Apr 2013
- 2.1-1822 Mar 2011
- 2.1-168 Nov 2009
- 2.1-155 Nov 2009
- 2.1-1414 Apr 2009
- 2.1-1329 Mar 2009
- 2.1-1213 Feb 2009
- 2.1-113 Feb 2009
- 2.1-1020 Jan 2009
- 2.1-98 Jan 2009
- 2.1-81 Feb 2008
- 2.1-721 Jan 2008
- 2.1-613 Sep 2007
- 2.1-424 May 2007
- 2.1-313 May 2007
- 2.1-213 May 2007
- 2.0-42 Nov 2006
- 2.0-36 Oct 2006
- 2.0-227 Jul 2006
- 2.0-129 May 2006
- 1.1-120 Feb 2006
- 1.1-015 Dec 2005
- 1.0-115 Nov 2005
- 1.0-05 Aug 2005
- 0.2-930 Jul 2005
- 0.2-831 May 2005
- 0.2-718 May 2005
- 0.2-625 Jan 2005
- 0.2-311 Sep 2004
- 0.2-215 May 2004
- 0.2-12 Feb 2004
- Released
- 5 Feb 2024R 4.3.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.
- 12none added or removed
Record made 30 Oct 2026, 07:21 UTC from data release v2026-10-29, merged 23:17 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.1-24, released 23 Feb 2026.
- Time between
- 749 days1 release in between
- Advisories
- None knownfor either release
- Exports
- No changebetween the two
- Files changed
- 10+71 −45 lines
Values that differ (2)
| Measure | Section | 2.1-22.1 | 2.1-24 |
|---|---|---|---|
| Authors | Release | Andrew Gelman, changes, Sibylle Sturtz, Gregor Gorjanc, Insightful Corp. | Andrew Gelman, Sibylle Sturtz, Uwe Ligges, Gregor Gorjanc, Jouni Kerman, Insightful Corp. |
| Suggests | Dependencies | BRugs (>= 0.3-2) | BRugs |
Most changed files (10 of 10)
| File | Lines added | Lines deleted |
|---|---|---|
DESCRIPTION | 42 | 16 |
MD5 | 12 | 12 |
vignettes/literatur.bib | 8 | 8 |
inst/doc/R2WinBUGS.Rnw | 3 | 3 |
vignettes/R2WinBUGS.Rnw | 3 | 3 |
man/openbugs.Rd | 2 | 2 |
R/conv.par.R | 1 | 1 |
build/vignette.rds | 0 | 0 |
data/schools.txt.gz | 0 | 0 |
inst/doc/R2WinBUGS.pdf | 0 | 0 |
Release
- Published
- 5 Feb 2024
- Status
- Replaced by 2.1-23 on 23 Jul 2025
- Previous
- 2.1-22, 16 Dec 2023
- License
- GPL-2, OSI approved
- Maintainer
- Uwe Ligges
- Download size
- 1.2 MB
- Authors
- Andrew Gelman, changes, Sibylle Sturtz, Gregor Gorjanc, Insightful Corp.
- 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
- 1,865
- Public exports
- 12
- Internal functions
- 17
- Mean complexity
- 8.4the most is 46
Lines by kind (6,311)
| Kind | Lines | Share |
|---|---|---|
| R code | 1,865 | 30% |
| Documentation | 1,056 | 17% |
| Guides | 3,390 | 54% |
Tests
- Test cases
- 0
- Lines of tests
- 0
- Exports named in tests
- 0%
- Tests
- No
- Test lines per line of code
- 0.00
- Coverage
- Not measured for this release
- Help pages with running examples
- 4 of 4
Documentation
- Exports documented
- 100%
- Arguments documented
- 97%
- Return value documented
- 88.9%
- Vignettes
- 1
- Help pages
- 21
- Exports with examples
- 44.4%
- NEWS
- Yes
- Citation file
- Yes, cites a publication
- 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
- R (>= 2.13.0), coda (>= 0.11-0), boot
- Imports
- utils, stats, graphics
- LinkingTo
- None
- Suggests
- BRugs (>= 0.3-2)
- 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 | 29 Oct 2026 |
| Advisories | osv-advisories 1.0.0, R version 4.6.1 (2026-06-24) | 29 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-29 (merged 23:17 UTC). Values not kept for a release say so and are never filled in from another release.