Go to file

Pavol Rusnak c6b9fa4873 legacy: support Signify Ed25519 signatures + add device test		5 years ago
ci	ci: split jobs based on stage not project	5 years ago
common	…
core	apps/wallet: support Signify Ed25519 signatures (#348 )	5 years ago
crypto	docs: switch http to https in links (#419 )	5 years ago
docs/git/hooks	…
legacy	legacy: support Signify Ed25519 signatures + add device test	5 years ago
python	…
storage	…
tests	legacy: support Signify Ed25519 signatures + add device test	5 years ago
tools	…
vendor	…
.clang-format	…
.gitignore	…
.gitlab-ci.yml	…
.gitmodules	…
.travis.yml	…
Makefile	…
Pipfile	python: clarify requirements, enable tox in CI	5 years ago
Pipfile.lock	…
README-monorepo.md	…
README.md	…
SECURITY.md	…
create_monorepo.py	…
setup.cfg	…
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.