temper

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.

There is a development branch ("develop") for interim development from which release branches are created.

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

Releases list at https://github.com/sramsay/temper/releases

Every release is tagged. See https://github.com/sramsay/temper/tags for a list of tags.

Non-trivial release notes file in repository: https://github.com/sramsay/temper/blob/master/ChangeLog.md

We have not detected any publicly known vulnerabilities, though we intend to document any such problems in the release notes: https://github.com/sramsay/temper/blob/master/ChangeLog.md

This project uses GitHub's issue tracker: https://github.com/sramsay/temper/issues

The project uses GitHub for reporting issues: https://github.com/sramsay/temper/issues

The project uses Github's issue tracker at https://github.com/sramsay/wwo/issues, which archives and allows for searching.

This project has no known vulnerabilities. However, future vulnerabilities would be reported in the https://github.com/sramsay/temper/blob/master/README.md file and in the release notes https://github.com/sramsay/temper/blob/master/ChangeLog.md when the problem is resolved.

We have not received any vulnerability reports for this project.

This project uses Meson and Ninja for builds, and contains all the necessary configuration files for creating the binary application from source.

The project is tested with a unit test suite (https://github.com/sramsay/temper/tree/master/test) which is part of the project. The test suite is released under the same license. The test suite uses Catch (https://github.com/philsquared/Catch) which is released under the Boost Software License 1.0, and Bats (https://github.com/sstephenson/bats) which is under an MIT license.

There seems to be a bug in meson that is preventing "ninja check" from finding the appropriate script for running the cli tests, but that is the goal. There's a workaround in place for the moment that allows the user to run the tests using an ordinary Makefile (make check).

This project uses Travis-CI for continuous integration (https://travis-ci.org/sramsay/temper)

https://github.com/sramsay/temper/blob/master/.github/CONTRIBUTING.md

https://github.com/sramsay/temper/blob/master/.github/CONTRIBUTING.md

https://github.com/sramsay/temper/blob/master/.github/CONTRIBUTING.md

clang-tidy on all builds.

The project builds with a wide variety of warning flags (-Wall -Winvalid-pch -Wnon-virtual-dtor -Wextra -Wpedantic) in both debug and release mode.

Stephen Ramsay is the primary developer. He has over twenty years of software development experience, and strives to adhere to the relevant principles. The software is also routinely checked for common vulnerabilities using https://lgtm.com/projects/g/sramsay/temper/?mode=list as part of the continuous integration process.

clang-tidy and Cppcheck are run all commits.

The code is constantly checked using clang-tidy, and with Cppcheck (on every commit) through Codacy, as well as lgtm (daily, on most recent commit).

Valgrind is run on all commits.

Valgrind is run regularly, and regularly fuzzed using iFuzz (https://github.com/google/syzkaller/tree/master/pkg/ifuzz)

This logic of this program is far too small to warrant the use of assertions, though the opportunity may arise.