kangaru

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.

Branches such as dev-4.1.x is a nightly version that is updated continuously and is tested by all our continuous integrations alerts and test suites.

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

We use semantic versioning for this project. The version number is exposed with cmake and with git tags.

https://github.com/gracicot/kangaru/releases

No vulnerability has been found in this library. Most of the code is in the form of a template, and if there is any vulnerability is caused by compiling a particular, valid instantiation, we will respond and fix the bug.

The GitHub interface permit any user to report bugs.

https://github.com/gracicot/kangaru/issues

The GitHub issue tracker tracks individual issues.

https://github.com/gracicot/kangaru/issues

https://github.com/gracicot/kangaru/issues?utf8=%E2%9C%93&q=

https://github.com/gracicot/kangaru/blob/master/README.md#contributing

https://github.com/gracicot/kangaru/blob/master/README.md#contributing

No vulnerability has been reported

Non-trivial build file in repository: https://github.com/gracicot/kangaru/blob/master/CMakeLists.txt.

Non-trivial build file in repository: https://github.com/gracicot/kangaru/blob/master/CMakeLists.txt.

This library support building using GCC and Clang

All our test are publicly available at this URL: https://github.com/gracicot/kangaru/tree/master/test/src All of them are run automatically on travis: https://travis-ci.org/gracicot/kangaru and appveyor: https://ci.appveyor.com/project/gracicot/kangaru

The command ctest will run all tests and report a summary

How code is mostly templates. There is only a few runtime branches and they are tested in multiple instantiation context.

https://travis-ci.org/gracicot/kangaru https://ci.appveyor.com/project/gracicot/kangaru https://bettercodehub.com/results/gracicot/kangaru

In our contributing guideline, we suggest adding tests when a functionality would benefit from it.

All major improvements have tests added for it in all versions that had automatic testing.

In the contribution guideline: https://github.com/gracicot/kangaru/blob/master/CONTRIBUTING.md#testing

Our examples and tests are compiled with warnings enabled.

Warnings are considered an issue that need to be addressed. If a warning is deemed useful and informative, we will commit to support this warning.

We are using -Wall and -Wextra on GCC and Clang. We are enabling /W3 on msvc.

One primary developer, Guillaume Racicot, passed a security course at ÉTS Montréal.

No network communication is done in this library

We do not use any communication between computers or other processes.

Github is using HTTPS and SSH to deliver downloads and clones

We commit to fix any major security issues within acceptable times and backport the fix on supported versions.

No password or any keys are registered inside the repository or documentation

We are using bettercodehub: https://bettercodehub.com/results/gracicot/kangaru codacy: https://app.codacy.com/project/gracicot/kangaru/dashboard and lgtm: https://lgtm.com/projects/g/gracicot/kangaru/

Both lgtm and codacy are using many guideline and diagnostic on how to fix security related issues and how to adopt a better style.

Every commit are analysed.

If any of our users find a vulnerability using such tool, we commit to address the issue as fast as possible. Upon integration of dynamic analysis, we will check every commit for issues.