arno/trezor-firmware
1
0
Fork 0
mirror of https://github.com/trezor/trezor-firmware.git synced 2024-11-16 04:29:08 +00:00
Code Issues Releases Wiki Activity
7,627 Commits 342 Branches 206 Tags 195 MiB
Python 34.6%
C 33.7%
Rust 29.4%
Nix 0.6%
C++ 0.4%
Other 1.1%
6f66ad9591
Go to file
Tomas Susanka 6f66ad9591
cardano: Implement SLIP-0023 and add SLIP-0039 support for Carda… (#359) 
cardano: Implement SLIP-0023 and add SLIP-0039 support for Cardano.
2019-07-26 12:00:53 +02:00
ci ci/legacy: don't build bootloader/demo in bitcoinonly+debug targets 2019-06-11 17:01:13 +02:00
common git subrepo push common 2019-07-25 12:34:59 +02:00
core cardano: Implement SLIP-0023 and add SLIP-0039 support for Cardano. 2019-07-25 19:43:05 +02:00
crypto cardano: Implement SLIP-0023 and add SLIP-0039 support for Cardano. 2019-07-25 19:43:05 +02:00
docs/git/hooks docs: set hook as executable 2019-07-12 12:55:48 +02:00
legacy legacy: replace load_device mnemonic to mnemonics 2019-07-24 17:04:54 +02:00
python tests: move shamir passphrase test to seperate file, add one more case 2019-07-24 17:23:08 +02:00
storage storage: fix incomatibility with new pytest 2019-07-09 14:47:24 +02:00
tools core/messages: don't generate unused messages 2019-07-01 15:52:36 +02:00
vendor
.clang-format core+legacy: rework code styling checks 2019-04-18 17:40:55 +02:00
.gitignore
.gitlab-ci.yml
.gitmodules
.travis.yml
create_monorepo.py
Makefile
Pipfile core/typing: add mypy 2019-07-09 12:51:48 +02:00
Pipfile.lock Pipenv: reinstall Pipfile.lock 2019-07-24 12:16:26 +02:00
README-monorepo.md
README.md
SECURITY.md add SECURITY.md 2019-06-06 19:50:57 +02:00
setup.cfg core/typing: add annotations 2019-07-09 12:51:48 +02:00
shell.nix nix: add coverage python package 2019-06-26 22:25:04 +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.