* using log directory 'd:/RCompile/CRANincoming/R-devel/upsetly.Rcheck'
* using R Under development (unstable) (2025-12-16 r89184 ucrt)
* using platform: x86_64-w64-mingw32
* R was compiled by
    gcc.exe (GCC) 14.3.0
    GNU Fortran (GCC) 14.3.0
* running under: Windows Server 2022 x64 (build 20348)
* using session charset: UTF-8
* checking for file 'upsetly/DESCRIPTION' ... OK
* this is package 'upsetly' version '0.0.1'
* package encoding: UTF-8
* checking CRAN incoming feasibility ... NOTE
Maintainer: 'Anbunensi User <an.bunengsi@qq.com>'

New submission

License components with restrictions and base license permitting such:
  MIT + file LICENSE

Possibly misspelled words in DESCRIPTION:
  Plotly (2:37)
  UpSet (2:20, 6:33)
  copyable (6:71)
* checking package namespace information ... OK
* checking package dependencies ... OK
* checking if this is a source package ... OK
* checking if there is a namespace ... OK
* checking for hidden files and directories ... OK
* checking for portable file names ... NOTE
Found the following non-portable file path:
  upsetly/docs/test_files/libs/quarto-html/quarto-syntax-highlighting-587c61ba64f3a5504c4d52d930310e48.css

Tarballs are only required to store paths of up to 100 bytes and cannot
store those of more than 256 bytes, with restrictions including to 100
bytes for the final component.
See section 'Package structure' in the 'Writing R Extensions' manual.
* checking whether package 'upsetly' can be installed ... OK
* checking installed package size ... OK
* checking package directory ... OK
* checking for future file timestamps ... OK
* checking DESCRIPTION meta-information ... WARNING
Invalid license file pointers: LICENSE
* checking top-level files ... NOTE
Non-standard file/directory found at top level:
  'docs'
* checking for left-over files ... OK
* checking index information ... OK
* checking package subdirectories ... OK
* checking code files for non-ASCII characters ... WARNING
Found the following file with non-ASCII characters:
  R/upsetly.R
Portable packages must use only ASCII characters in their R code and
NAMESPACE directives, except perhaps in comments.
Use \uxxxx escapes for other characters.
Function 'tools::showNonASCIIfile' can help in finding non-ASCII
characters in files.
* checking R files for syntax errors ... OK
* checking whether the package can be loaded ... OK
* checking whether the package can be loaded with stated dependencies ... OK
* checking whether the package can be unloaded cleanly ... OK
* checking whether the namespace can be loaded with stated dependencies ... OK
* checking whether the namespace can be unloaded cleanly ... OK
* checking loading without being on the library search path ... OK
* checking use of S3 registration ... OK
* checking dependencies in R code ... OK
* checking S3 generic/method consistency ... OK
* checking replacement functions ... OK
* checking foreign function calls ... OK
* checking R code for possible problems ... NOTE
upsetly: no visible global function definition for '%>%'
upsetly: no visible binding for global variable '.combo_key'
upsetly: no visible binding for global variable 'count'
upsetly: no visible global function definition for 'desc'
upsetly: no visible binding for global variable 'set'
upsetly: no visible binding for global variable 'combo_index'
upsetly: no visible global function definition for 'setNames'
upsetly: no visible binding for global variable 'value'
upsetly: no visible binding for global variable 'y'
Undefined global functions or variables:
  %>% .combo_key combo_index count desc set setNames value y
Consider adding
  importFrom("stats", "setNames")
to your NAMESPACE file.
* checking Rd files ... OK
* checking Rd metadata ... OK
* checking Rd line widths ... OK
* checking Rd cross-references ... OK
* checking for missing documentation entries ... OK
* checking for code/documentation mismatches ... OK
* checking Rd \usage sections ... OK
* checking Rd contents ... OK
* checking for unstated dependencies in examples ... OK
* checking examples ... OK
* checking PDF version of manual ... [18s] OK
* checking HTML version of manual ... OK
* DONE
Status: 2 WARNINGs, 4 NOTEs