Older releaseCurrent release 1.8.9
stringi
‹1.8.7
- 1.8.94 Aug 2026, current
- 1.8.727 Mar 2025
- 1.8.46 May 2024
- 1.8.311 Dec 2023
- 1.8.223 Nov 2023
- 1.8.113 Nov 2023
- 1.7.1211 Jan 2023
- 1.7.811 Jul 2022
- 1.7.629 Nov 2021
- 1.7.54 Oct 2021
- 1.7.425 Aug 2021
- 1.7.316 Jul 2021
- 1.7.214 Jul 2021
- 1.6.217 May 2021
- 1.6.110 May 2021
- 1.5.39 Sep 2020
- 1.4.617 Feb 2020
- 1.4.511 Jan 2020
- 1.4.49 Jan 2020
- 1.4.313 Mar 2019
- 1.3.113 Feb 2019
- 1.2.420 Jul 2018
- 1.2.312 Jun 2018
- 1.2.22 May 2018
- 1.1.712 Mar 2018
- 1.1.617 Nov 2017
- 1.1.57 Apr 2017
- 1.1.321 Mar 2017
- 1.1.21 Oct 2016
- 1.1.127 May 2016
- 1.0-122 Oct 2015
- 0.5-529 Jun 2015
- 0.5-428 Jun 2015
- 0.5-222 Jun 2015
- 0.4-114 Dec 2014
- 0.3-16 Nov 2014
- 0.2-516 May 2014
- 0.2-415 May 2014
- 0.2-314 May 2014
- 0.1-2512 Mar 2014
- Released
- 27 Mar 2025R 4.4.3 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%.
- –no tests to run
- 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.
- 256none added or removed
Record made 30 Oct 2026, 20:58 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 1.8.9, released 4 Aug 2026.
- Time between
- 495 daysno release in between
- Advisories
- None knownfor either release
- Exports
- No changebetween the two
- Files changed
- 279+1,991 −2,629 lines
Values that differ (1)
| Measure | Section | 1.8.7 | 1.8.9 |
|---|---|---|---|
| Lines of compiled code | Code | 540,714, 96.3% of code | 540,729, 96.3% of code |
Most changed files (12 of 279)
| File | Lines added | Lines deleted |
|---|---|---|
configure | 521 | 1,035 |
MD5 | 276 | 278 |
configure.ac | 66 | 139 |
man/about_search.Rd | 41 | 41 |
man/stri_locate_boundaries.Rd | 31 | 31 |
man/stri_trans_casemap.Rd | 29 | 29 |
man/stri_extract_boundaries.Rd | 28 | 28 |
man/about_search_boundaries.Rd | 27 | 27 |
man/stri_split_boundaries.Rd | 27 | 27 |
src/icu74/common/udata.cpp | 28 | 26 |
man/stri_count_boundaries.Rd | 26 | 26 |
man/stri_wrap.Rd | 25 | 25 |
Release
- Published
- 27 Mar 2025
- Status
- Replaced by 1.8.9 on 4 Aug 2026
- Previous
- 1.8.4, 6 May 2024
- License
- file LICENSE
- Maintainer
- Marek Gagolewski
- Download size
- 11.4 MB
- Authors
- Marek Gagolewski, Bartek Tartanus, Unicode, Inc. and others
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
- 11,024
- Public exports
- 256
- Internal functions
- 15
- Mean complexity
- 2.1the most is 13
Lines by kind (561,578)
| Kind | Lines | Share |
|---|---|---|
| R code | 11,024 | 2% |
| Documentation | 9,840 | 2% |
| Compiled code | 540,714 | 96% |
Tests
- Test cases
- 0
- Lines of tests
- 0
- Exports named in tests
- 0%
- Tests
- No
- Test lines per line of code
- 0.00
- Coverage
- No tests to run
- Help pages with running examples
- 70 of 73
Documentation
- Exports documented
- 91.4%
- Arguments documented
- 91.2%
- Return value documented
- 100%
- Vignettes
- 0
- Help pages
- 102
- Exports with examples
- 79.3%
- NEWS
- Yes
- Citation file
- Yes, cites a publication
- 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
- R (>= 3.4)
- Imports
- tools, utils, stats
- 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 3.6.5 on R 4.6.1 | run on 1.8.7 |
| 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.