tiltdens 0.2.0 to 0.2.1
CRANRecord of 0.2.0Record of 0.2.1Both records side by side
- 0.2.0 and 0.2.1
- other releases
- daily mean, day by day
- after this copy’s series ends on 26 Oct 2026
No release lies between 0.2.0 and 0.2.1.
- Time between
- 4 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
- SameMIT + file LICENSE
- Maintainer
- SameHassan Doosti
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.1 2 to 28 Oct 2026, still the newest | 27 | 25 | 442 | 18 |
| 0.2.0 28 Sep to 1 Oct 2026 | 4 | 76 | 19 |
0.2.0 has 4 days counted, so its daily mean covers only those days.
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.0 | 0.2.1 | Change |
|---|---|---|---|
| Lines of R code | 2,996 | 3,098 | +102 up |
| Files | 62 | 64 | +2 up |
| Internal functions | 63 | 67 | +4 up |
| Download size | 96 KB | 98 KB | +2 KB up |
| Source, unpacked | 286 KB | 295 KB | +9 KB up |
4 other figures of the code are the same in both.
Side by side
| Measure | 0.2.0 | 0.2.1 | Change |
|---|---|---|---|
| Lines of R code | 2,996 | 3,098 | +102 |
| Lines of compiled code | 0 | 0 | |
| Files | 62 | 64 | +2 |
| Public exports | 18 | 18 | |
| Internal functions | 63 | 67 | +4 |
| Mean complexity | 4.2 | 4.2 | |
| Highest complexity | 20 | 20 | |
| Download size | 96 KB | 98 KB | +2 KB |
| Source, unpacked | 286 KB | 295 KB | +9 KB |
| Analysed with | rpkg-analyzer 0.5.2 | rpkg-analyzer 0.5.2 |
Tests
Method, tests Method Test coverage is measured by downloading each CRAN package's current source file, installing its dependencies, building it and running its tests under covr.Test coverage
| Measure | 0.2.0 | 0.2.1 | Change |
|---|---|---|---|
| Lines run by tests | 88.0% | 88.3% | +0.3 points up |
| Test cases | 81 | 84 | +3 up |
| Lines of tests | 949 | 984 | +35 up |
2 other figures of the tests are the same in both.
Side by side
| Measure | 0.2.0 | 0.2.1 | Change |
|---|---|---|---|
| Lines run by tests | 88.0% | 88.3% | +0.3 points |
| Test cases | 81 | 84 | +3 |
| Lines of tests | 949 | 984 | +35 |
| Test lines per line of code | 0.32 | 0.32 | |
| Exports named in tests | 94.4% | 94.4% |
Documentation
| Measure | 0.2.0 | 0.2.1 | Change |
|---|---|---|---|
| Arguments documented | 77.0% | 77.3% | +0.3 points up |
| Lines of documentation | 1,042 | 1,124 | +82 up |
3 other figures of the documentation are the same in both.
Side by side
| Measure | 0.2.0 | 0.2.1 | Change |
|---|---|---|---|
| Exports documented | 100.0% | 100.0% | |
| Arguments documented | 77.0% | 77.3% | +0.3 points |
| Return value documented | 100.0% | 100.0% | |
| Lines of documentation | 1,042 | 1,124 | +82 |
| Lines of guides | 323 | 323 |
Files changed
- Files changed
- 12in 0.2.1
- Lines added
- 301
- Lines deleted
- 66
Most changed files (12 of 12)
| File | Lines added | Lines deleted |
|---|---|---|
R/kernel_registry.R | 130 | 34 |
tests/testthat/test-revision.R | 40 | 5 |
man/make_kernel.Rd | 28 | 13 |
man/summary.tilt_kernel.Rd | 41 | 0 |
man/plot.tilt_kernel.Rd | 26 | 0 |
MD5 | 11 | 9 |
NEWS.md | 11 | 0 |
DESCRIPTION | 3 | 3 |
R/tilt_cv.R | 4 | 1 |
R/tilt.R | 3 | 1 |
NAMESPACE | 3 | 0 |
R/sharpen.R | 1 | 0 |
Each release is counted against the release before it, so a line changed twice counts twice.
Release notes
From the NEWS file of 0.2.1. Only the section for the newest release on record is kept.
make_kernel()now checks that the kernel is a symmetric probability density and stops with an explanation if it is not;check = FALSEbuilds an unsuitable kernel for inspection only.tilt_density(),tilt_density_cv(),tilt_cv()andsharpen_density()refuse such a kernel, so it cannot be used for estimation by mistake.- Kernel objects gain
summary()andplot()methods.summary()returns the propertiescheck_kernel()reports, as an object;check_kernel()is now a thin wrapper that prints it.
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.
Checks, the install tree, dependents and the repository describe the package as it is now, so they are on the package page.