遵循以下最佳实践的项目将能够自愿的自我认证,并显示他们已经实现了核心基础设施计划(OpenSSF)徽章。 显示详细资料
[](https://www.bestpractices.dev/projects/7096)
<a href="https://www.bestpractices.dev/projects/7096"><img src="https://www.bestpractices.dev/projects/7096/badge"></a>
Bayesian Additive Regresssion Kernels for Bayesian Nonparametric estimation of functions in arbitrary dimensions for continuous and binary response variables.
https://github.com/merliseclyde/bark/blob/master/CONTRIBUTING.md
https://github.com/merliseclyde/bark/blob/master/CODE_OF_CONDUCT.md
https://merliseclyde.github.io/bark/authors.html lists all project contributors and their roles.
As a FLOSS project for R, it is easy for anyone to fork/clone the project and assume maintenance even without access to the behind-the-scenes elements of the githup repository. CRAN has been known many times to allow new users to assume maintenance of orphaned projects. THIS github repo may be defunct, but it can be cloned, updated, and the corrections built into the package and pushed to CRAN seamlessly to the end user.
See https://cran.r-project.org/src/contrib/Orphaned/README
Two other contributors. And as a FLOSS project for R, anyone may fork/clone the project and assume maintenance with permission from CRAN even without access to the behind-the-scenes elements of the GitHub repository: See https://cran.r-project.org/doc/manuals/r-release/R-exts.html
Project roadmap is at https://github/merliseclyde/bark/README.md with more specifics about tasks under the Issue tracker https://github/merliseclyde/bark/issues
All R packages on CRAN must conform to https://cran.r-project.org/doc/manuals/r-release/R-exts.html
https://github.com/merliseclyde/bark/SECURITY.md
https://merliseclyde.github.io/bark/
All code documentation uses Roxygen2 and checks in building the package for R ensure that the documentation agrees with source code function arguments. In addition the updated webpage for the project is updated with every push to GitHuB with Github Actions, which deploy the website.
https://merliseclyde.github.io/bark https://github.com/merliseclyde/bark
Input and output (text based) to use the package is controlled by R and the user. Graphics parameters can be set for a colorblind pallet and use symbols in addition to color for display.
This is provided by R for R and C messages as documented at https://cran.r-project.org/doc/manuals/r-release/R-exts.html#Internationalization
no passwords are stored
Previous versions are available on Github and CRAN Archives, with corresponding R requirements for building
https://github.com/merliseclyde/bark/issues
All reports submitted as issues will be credited in the repository NEWS.md as soon as they are addressed
https://github.com/merliseclyde/bark/blob/master/SECURITY.md
https://merliseclyde.github.io/bark/CONTRIBUTING.html
There is no automated method at this time; FLOSS tools may be run manually at the time packages are submitted
R CMD check --as-cran is language standard
Standards for CRAN apply for building with debugging with R
Not applicable for R
Not applicable for the package source files; no random seeds are set by the code but are obtained from the scripting language within R
Installs from CRAN or uses install.packages or package manager within R. Instructions for installing from GitHub are on the package website: https://merliseclyde.github.io/bark
install.packages
Installs from CRAN or uses install.packages or package manager within R which supports default/custom installation directories. Instructions for installing from GitHub are on the package website: https://merliseclyde.github.io/BAS
Installs from CRAN or uses install.packages or package manager within R. Instructions for installing from GitHub are on the package website: https://github.com/merliseclyde/BAS.
DESCRIPTION file for R: https://github.com/merliseclyde/bark/blob/master/DESCRIPTION lists all package dependencies
External dependencies checked on CRAN; https://cran.r-project.org/web/checks/check_results_bark.html. Project maintainer is notified of vulnerabilities in dependencies
Uses standard components provided by R and contributed packages available through R
Uses APIs through R for FLOSS math libraries, etc
Uses Github Actions on the main branch on every commit. Passing Badge for master branch is shown on < https://github.com/merliseclyde/barkblob/master/README.md>. https://github.com/merliseclyde/bark/actions
Test suite in https://github.com/merliseclyde/bark/tree/master/tests
https://codecov.io/github/merliseclyde/bark?branch=master
https://github.com/merliseclyde/bark/blob/master/.github/CONTRIBUTING.md
required by CRAN hosting
Installation is secure; other aspects NA for R packages.
Releases on CRAN include the file MD5 which is checked when packages are installed
https://gist.github.com/hollodotme/edc4d4613ca602e70d242eae8b0a25cc
Test suite checks inputs: https://github.com/merliseclyde/bark/tree/master/tests; in general no restrictions on data
Vulnerabilities are not likely in interpreted R code; C source code uses checks and address sanitizers to identify security vulnerabilities. Any vulnerabilities in C code are checked by the main repository and are required to be fixed or the project will be removed.
See https://github.com/merliseclyde/bark/SECURITY.md
R CMD check with valgrind is used to check for memory/buffer vulnerabilities as well as using R with other address sanitizers see http://dirk.eddelbuettel.com/code/sanitizers.html using hub
hub
后退