Go to file

Tomas Susanka 582910732a core/slip39: one more typo		5 years ago
ci	ci/legacy: don't build bootloader/demo in bitcoinonly+debug targets	5 years ago
common	git subrepo push common	5 years ago
core	core/slip39: one more typo	5 years ago
crypto	core: add slip39 keyboard	5 years ago
legacy	legacy: detect CALLBACK fields and fail build when found	5 years ago
python	tests: fix recovery device tests due to additional screen	5 years ago
storage	all: rename TREZOR to Trezor where possible	5 years ago
tools	…
vendor	…
.clang-format	…
.gitignore	…
.gitlab-ci.yml	…
.gitmodules	submodules: remove secp256k1-zkp's branch name because it will rotate	5 years ago
.travis.yml	…
Makefile	…
Pipfile	…
Pipfile.lock	…
README-monorepo.md	…
README.md	…
SECURITY.md	add SECURITY.md	5 years ago
create_monorepo.py	…
setup.cfg	python: more consistent handling of markers in device_tests	5 years ago
shell.nix	…

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.