arno/trezor-firmware
1
0
Fork 0
mirror of https://github.com/trezor/trezor-firmware.git synced 2024-11-25 08:58:14 +00:00
Code Issues Releases Wiki Activity
8,199 Commits 353 Branches 205 Tags 210 MiB
Python 34.6%
C 33.7%
Rust 29.4%
Nix 0.6%
C++ 0.4%
Other 1.1%
b25537f6b0
Go to file
matejcik b25537f6b0 core: nicer output for cancellations
2019-10-22 16:54:49 +02:00
ci ci: run mypy without limitation 2019-10-22 14:36:25 +00:00
common core: add final mypy fixes! 2019-10-22 14:36:25 +00:00
core core: nicer output for cancellations 2019-10-22 16:54:49 +02:00
crypto all: let's use -Wno-missing-braces because clang does not respect 2019-10-11 09:59:32 +02:00
docs/git/hooks
legacy legacy/signing.c: Revert formatting of the workflow of streamed signing. 2019-10-11 11:20:02 +02:00
python core: add final mypy fixes! 2019-10-22 14:36:25 +00:00
storage all: let's use -Wno-missing-braces because clang does not respect 2019-10-11 09:59:32 +02:00
tests tests: add multisig marker 2019-10-22 14:32:38 +00:00
tools
vendor vendor: add testsuite for FIDO2; regenerate Pipfile 2019-10-17 16:32:50 +00:00
.clang-format
.gitignore
.gitlab-ci.yml gitlab-ci: checking if pipenv exists 2019-10-16 10:27:27 +02:00
.gitmodules vendor: add testsuite for FIDO2; regenerate Pipfile 2019-10-17 16:32:50 +00:00
.travis.yml
build-docker.sh
create_monorepo.py
Makefile
Pipfile pip: use hypothesis==4.38.1 and attrs==18.2.0 2019-10-21 11:44:17 +00:00
Pipfile.lock pip: use hypothesis==4.38.1 and attrs==18.2.0 2019-10-21 11:44:17 +00:00
README-monorepo.md
README.md
SECURITY.md
setup.cfg
shell.nix nix: let's install clang instead of clang-tools 2019-10-18 17:31:57 +00: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.