arno/trezor-firmware
1
0
Fork 0
mirror of https://github.com/trezor/trezor-firmware.git synced 2024-10-16 21:09:06 +00:00
Code Issues Releases Wiki Activity
7,899 Commits 321 Branches 205 Tags 196 MiB
Python 34.6%
C 33.7%
Rust 29.4%
Nix 0.6%
C++ 0.4%
Other 1.1%
bfe01707b1
Go to file
Pavol Rusnak bfe01707b1
build: add BITCOIN_ONLY variable to docker build scripts
2019-09-04 12:16:55 +02:00
ci ci: add "regular" to regular builds 2019-09-02 13:45:59 +02:00
common common: add blockbook link to cpuchain (#477) 2019-09-01 18:23:01 +02:00
core build: add BITCOIN_ONLY variable to docker build scripts 2019-09-04 12:16:55 +02:00
crypto crypto: fix valgrind issue with ed25519-donna, clean local variables 2019-08-30 17:21:15 +02:00
docs/git/hooks
legacy build: add BITCOIN_ONLY variable to docker build scripts 2019-09-04 12:16:55 +02:00
python build: make gen 2019-09-02 08:25:58 +02:00
storage storage: explicitly reseed in PRNG tests 2019-08-12 12:57:25 +02:00
tests tests: fix test_msg_binance_sign_tx.py 2019-09-03 15:11:50 +02:00
tools
vendor
.clang-format
.gitignore
.gitlab-ci.yml
.gitmodules
.travis.yml
create_monorepo.py
Makefile
Pipfile
Pipfile.lock python: clarify requirements, enable tox in CI 2019-08-12 12:57:25 +02:00
README-monorepo.md
README.md
SECURITY.md
setup.cfg
shell.nix nix: we need pytest-random-order now 2019-09-01 13:43:36 +02:00

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.