Go to file

Tomas Susanka b7d2fa9643 core: add Binance to 2.1.5 changelog		5 years ago
ci	ci: add "regular" to regular builds	5 years ago
common	common: add blockbook link to cpuchain (#477 )	5 years ago
core	core: add Binance to 2.1.5 changelog	5 years ago
crypto	crypto: fix valgrind issue with ed25519-donna, clean local variables	5 years ago
docs/git/hooks	…
legacy	legacy: refactor SKIPPED_MESSAGES in the Makefile	5 years ago
python	build: make gen	5 years ago
storage	…
tests	tests: fix test_msg_binance_sign_tx.py	5 years ago
tools	ci: include version+githash into artefact filenames	5 years ago
vendor	…
.clang-format	…
.gitignore	…
.gitlab-ci.yml	ci: split jobs based on stage not project	5 years ago
.gitmodules	…
.travis.yml	…
Makefile	build: add help to make style/style_check	5 years ago
Pipfile	python: clarify requirements, enable tox in CI	5 years ago
Pipfile.lock	python: clarify requirements, enable tox in CI	5 years ago
README-monorepo.md	…
README.md	…
SECURITY.md	docs: use monospace for fingerprints	5 years ago
create_monorepo.py	…
setup.cfg	tests: run default set of tests from root	5 years ago
shell.nix	nix: we need pytest-random-order now	5 years ago

README.md

Trezor Firmware

Contribute

Inspired by GitLab Contributing Guide

Security vulnerability disclosure

Please report suspected security vulnerabilities in private to security@satoshilabs.com, also see the disclosure section on the Trezor.io website. Please do NOT create publicly viewable issues for suspected security vulnerabilities.

Issue Labels

Priority

Label	Meaning (SLA)
P1 Urgent	The current release + potentially immediate hotfix (30 days)
P2 High	The next release (60 days)
P3 Medium	Within the next 3 releases (90 days)
P4 Low	Anything outside the next 3 releases (120 days)

Severity

Label	Impact
S1 Blocker	Outage, broken feature with no workaround
S2 Critical	Broken feature, workaround too complex & unacceptable
S3 Major	Broken feature, workaround acceptable
S4 Low	Functionality inconvenience or cosmetic issue

CI

The complete test suite is running on our internal GitLab CI. If you are an external contributor, we also have a Travis instance where a small subset of tests is running as well - mostly style and easy fast checks, which are quite common to fail for new contributors.