arno/trezor-firmware
1
0
Fork 0
mirror of https://github.com/trezor/trezor-firmware.git synced 2024-11-05 23:10:12 +00:00
Code Issues Releases Wiki Activity
8,153 Commits 330 Branches 205 Tags 247 MiB
Python 34.6%
C 33.7%
Rust 29.4%
Nix 0.6%
C++ 0.4%
Other 1.1%
76f20fbaa5
Go to file
Marek Mahut 76f20fbaa5 ci/build: adding darwin emulator build 
Keeping as allow_failure until it is fully tested out
2019-10-16 10:27:27 +02:00
ci ci/build: adding darwin emulator build 2019-10-16 10:27:27 +02:00
common
core
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
python common/defs: add ZCR (#611) 2019-10-11 21:01:11 +02:00
storage
tests debug: Add left and right swipe direction to DebugLinkDecision message and unify terminology around swipe direction. 2019-10-10 14:56:49 +02:00
tools
vendor
.clang-format style: fix weirdness in modtrezorio-fatfs.h 2019-09-12 16:49:51 +02:00
.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
README.md
SECURITY.md
setup.cfg
shell.nix shell.nix: adding darwin frameworks 2019-10-16 10:27:27 +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.