covid19ita

Repository on GitHub, which provides public git repositories with URLs.

Repository on GitHub, which uses git. git can track the changes, who made them, and when they were made.

the project follow the gitflow convention, including a master branch for the official releases, a develop branch for interim releases.

Repository on GitHub, which uses git. git is distributed.

Repository on GitHub, releases are tagged using the convention v-..

Repository on GitHub, releases are tagged using the convention v-..

Non-trivial release notes file in repository: https://github.com/UBESP-DCTV/covid19ita/blob/master/NEWS.md.

there have been no publicly known vulnerabilities

Repository on GitHub which has issues tracker (https://github.com/UBESP-DCTV/covid19ita/issues)

Repository on GitHub which has issues tracker (https://github.com/UBESP-DCTV/covid19ita/issues)

All the bugs reported have been solved

Oldest current open enhancement requests is 27 days ago (open by the developer); All the enhancement requests opened by a non-developer subject have been solved.

Repository on GitHub which has issue tracker. All the issues are labelled accordingly to bug, enhancement request, or other tags of interest https://github.com/UBESP-DCTV/covid19ita/issues?q=is%3Aissue+is%3Aclosed

https://github.com/UBESP-DCTV/covid19ita

README section "Bug reports"

vulnerability reports are always public

Currently, there is no vulnerability report

The project is an R package mainly, instruction about how to download, build and install it are reported in the README (https://github.com/UBESP-DCTV/covid19ita/tree/develop)

RTools + R package {remotes} are the sugested instruments, which are currently the most common tools across the R community for packages hosted on GHitHub

RTools + R package {remotes} are provided under FLOSS

automated test on Travis CI (https://travis-ci.com/UBESP-DCTV/covid19ita) and AppVeyor (https://ci.appveyor.com/project/CorradoLanera/covid19ita)

R CMD check

All the pushes in every branch trigger all the tests

automated test on Travis CI (https://travis-ci.com/UBESP-DCTV/covid19ita) and AppVeyor (https://ci.appveyor.com/project/CorradoLanera/covid19ita)

The project use the {testthat} package interface to develop the tests, which are all triggered at any R CMD check.

Repository on GitHub, which mark all the commit tested with badges regarding tests. Moreover, badges are reported in the README for automated test and build by Travis-CI, AppVeyor and test coverage

{covr} will automatically check %coverage and diff % coverage at any push/pull-request. thresholds are set to admit merging

run-time and development-time test are run automatically at every push/pull-request, as well as linter checks

The project CI is set up to convert warning in errors during automated tests, to be sure that pull requests are all free of errors and warnings

The project CIs are set up to convert warning in errors during automated tests, to be sure that pull requests are all free of errors and warnings, Moreover, it is internally strongly required (even if not mandatory) that R CMD check do not produce any notes too.

The project has no need to directly use cryptographic capabilities.

The project does not use/require cryptographic capabilities.

The project does not use/require cryptographic capabilities.

The project does not use/require security mechanisms other than GitHub access (ie through https or ssh) or to the website host for the app (https)

The project does not use/require security mechanisms other than GitHub access (ie through https or ssh) or to the website host for the app (https)

The project does not use/require security mechanisms other than GitHub access (ie through https or ssh) or to the website host for the app (https)

The project does not use/require security mechanisms other than GitHub access (ie through https or ssh) or to the website host for the app (https)

The project does not use/require security mechanisms other than GitHub access (ie through https or ssh) or to the website host for the app (https). No authentication is required (other than for GitHub access).

The project does not use/require security mechanisms other than GitHub access (ie through https or ssh) or to the website host for the app (https)

Delivery of the package passes through GitHub only, ie https or ssh.

anything is retrieved over http

Currently, there a no publicly known vulnerabilities

Currently, there a no publicly known vulnerabilities

No password is stored in the public repository on GitHub. Public access is limited to push/admin only, all the push/admin enabled developers are required to have 2FA enabled.

lintr is adopted and automated after every successful push/pull-request

lintr is adopted and automated after every successful push/pull-request

lintr is adopted and automated after every successful push/pull-request (branches will not merged if severity exploitable vulnerabilities will be discovered)

lintr is adopted and automated after every successful push/pull-request

{testthat} package and {assertive} package are used for run-time and development-time testing. All test are runner automatically at every push/pull-request and branches will not be merged if any test fails

project does not produce software written in a memory-unsafe language

{testthat} package and {assertive} package are used for development-time and run-time testing respectively. All test are runner automatically at every push/pull-request and branches will not be merged if any test fails.

{testthat} package and {assertive} package are used for development-time and run-time testing respectively. All test are runner automatically at every push/pull-request and branches will not be merged if any test fails