arno/trezor-firmware
1
0
Fork 0
mirror of https://github.com/trezor/trezor-firmware.git synced 2024-10-12 19:09:10 +00:00
Code Issues Releases Wiki Activity
7,774 Commits 317 Branches 205 Tags 188 MiB
Python 34.6%
C 33.7%
Rust 29.4%
Nix 0.6%
C++ 0.4%
Other 1.1%
d0ce2b9e39
Go to file
Tomas Susanka d0ce2b9e39 core: fix initialized to be unrelated to recovery 
closes #387
2019-08-21 14:10:36 +02:00
ci legacy: fix emulator bitcoin only build 2019-08-21 10:25:56 +02:00
common common/tools: reorder coins in coin_info.py so Regtest appears at the beginning 2019-08-21 11:06:02 +02:00
core core: fix initialized to be unrelated to recovery 2019-08-21 14:10:36 +02:00
crypto docs: switch http to https in links (#419) 2019-08-16 17:28:15 +02:00
docs/git/hooks
legacy legacy: fix emulator bitcoin only build 2019-08-21 10:25:56 +02:00
python common: introduce Features.features enum 2019-08-20 14:38:31 +02:00
storage
tests legacy: support Signify Ed25519 signatures + add device test 2019-08-19 18:11:08 +02:00
tools tools: different order of columns in to csv converter 2019-08-16 15:20:00 +02:00
vendor
.clang-format
.gitignore
.gitlab-ci.yml ci: split jobs based on stage not project 2019-08-19 14:47:12 +02:00
.gitmodules
.travis.yml
create_monorepo.py
Makefile
Pipfile python: clarify requirements, enable tox in CI 2019-08-12 12:57:25 +02:00
Pipfile.lock python: clarify requirements, enable tox in CI 2019-08-12 12:57:25 +02:00
README-monorepo.md
README.md
SECURITY.md docs: use monospace for fingerprints 2019-08-16 18:47:46 +02:00
setup.cfg tests: run default set of tests from root 2019-08-12 12:57:25 +02:00
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.