arno/trezor-firmware
1
0
Fork 0
mirror of https://github.com/trezor/trezor-firmware.git synced 2025-04-05 01:45:44 +00:00
Code Issues Releases Wiki Activity
8,130 Commits 467 Branches 212 Tags 265 MiB
Python 34.6%
C 33.7%
Rust 29.4%
Nix 0.6%
C++ 0.4%
Other 1.1%
9a641b6b01
Go to file
Andrew Kozlik 9a641b6b01 core/sd-protect: Allow user to retry if write fails.
2019-10-10 12:17:36 +02:00
ci
common
core core/sd-protect: Allow user to retry if write fails. 2019-10-10 12:17:36 +02:00
crypto crypto: explicitly initialize variable length arrays 2019-10-09 17:05:34 +02:00
docs/git/hooks
legacy legacy: refactor readprotobufint() 2019-10-09 15:48:52 +00:00
python
storage
tests
tools
vendor
.clang-format
.gitignore
.gitlab-ci.yml
.gitmodules
.travis.yml
build-docker.sh
create_monorepo.py
Makefile
Pipfile
Pipfile.lock pipfile: update dependencies 2019-10-08 19:28:10 +00:00
README-monorepo.md fix link in readme 2019-04-29 19:11:44 +02:00
README.md
SECURITY.md
setup.cfg mypy: add show_error_codes to setup.cfg 2019-10-02 11:12:34 +02:00
shell.nix build: update protobuf dependency to 3.6.1 2019-10-02 13:07:48 +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.