bujar 0.2-10 to 0.2-11
CRANRecord of 0.2-10Record of 0.2-11Both records side by side
- 0.2-10 and 0.2-11
- other releases
- daily mean, in 30-day steps
- after this copy’s series ends on 26 Oct 2026
No release lies between 0.2-10 and 0.2-11.
- Time between
- 170 daysno release between
- 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 either release
- Exports, method
- No changebetween the two
- Dependencies
- No changein any field
- Licence
- SameGPL-2
- Maintainer
- SameZhu Wang
Downloads while newest
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
| Release | Days newest | Days counted | CRAN downloads | Daily mean |
|---|---|---|---|---|
| 0.2-11 25 Jun 2023 to 28 Oct 2026, still the newest | 1,222 | 1,220 | 15,703 | 13 |
| 0.2-10 6 Jan to 24 Jun 2023 | 170 | 2,656 | 16 |
Daily mean while newest, 0.2-11 −17.6% down since 0.2-10
Counted on the CRAN mirror from each release's day to the day before the next release. This copy's daily series ends on 26 Oct 2026, so a span that runs past it is counted to that day and its daily mean covers the days counted. Other channels repackage on their own schedules, so they are not split by release.
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.
| Measure | 0.2-10 | 0.2-11 | Change |
|---|---|---|---|
| Source, unpacked | 2.8 MB | 2.8 MB | −1 KB down |
8 other figures of the code are the same in both.
Side by side
| Measure | 0.2-10 | 0.2-11 | Change |
|---|---|---|---|
| Lines of R code | 1,086 | 1,086 | |
| Lines of compiled code | 0 | 0 | |
| Files | 36 | 36 | |
| Public exports | 2 | 2 | |
| Internal functions | 18 | 18 | |
| Mean complexity | 12.0 | 12.0 | |
| Highest complexity | 113 | 113 | |
| Download size | 2.6 MB | 2.6 MB | |
| Source, unpacked | 2.8 MB | 2.8 MB | −1 KB |
| Analysed with | rpkg-analyzer 0.5.2 | rpkg-analyzer 0.5.2 |
Documentation
| Measure | 0.2-10 | 0.2-11 | Change |
|---|---|---|---|
| Lines of documentation | 226 | 236 | +10 up |
4 other figures of the documentation are the same in both.
Side by side
| Measure | 0.2-10 | 0.2-11 | Change |
|---|---|---|---|
| Exports documented | 100.0% | 100.0% | |
| Arguments documented | 100.0% | 100.0% | |
| Return value documented | 50.0% | 50.0% | |
| Lines of documentation | 226 | 236 | +10 |
| Lines of guides | 450 | 450 |
Files changed
- Files changed
- 8in 0.2-11
- Lines added
- 58
- Lines deleted
- 90
Most changed files (8 of 8)
| File | Lines added | Lines deleted |
|---|---|---|
inst/doc/dlbcl_raw.R | 0 | 78 |
inst/CITATION | 35 | 0 |
MD5 | 6 | 6 |
man/bujar.Rd | 10 | 0 |
DESCRIPTION | 4 | 4 |
R/rif.R | 2 | 2 |
NAMESPACE | 1 | 0 |
inst/doc/dlbcl.pdf | 0 | 0 |
Each release is counted against the release before it, so a line changed twice counts twice.
Unchanged and not compared
Dependencies, exports, licence, maintainer and the people named are the same in both releases. No advisory is known for either release. Neither release has tests.
Checks, the install tree, dependents and the repository describe the package as it is now, so they are on the package page.