You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
 
 
Go to file
Pavol Rusnak 07ef01f3e4
core: introduce BITCOIN_ONLY flag
5 years ago
ci ci: use explicit artifacts (don't use untracked: true) 5 years ago
common common/defs: add Umbru (#433) 5 years ago
core core: introduce BITCOIN_ONLY flag 5 years ago
crypto docs: switch http to https in links (#419) 5 years ago
docs/git/hooks
legacy tests: make path to tested binary configurable 5 years ago
python python: make gen_check fail if coins.json are outdated 5 years ago
storage
tests tests: add one more altcoin marker 5 years ago
tools tools/csv: modify weight 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
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

README.md

Trezor Firmware

img

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.