arno
/
trezor-firmware
mirror of https://github.com/trezor/trezor-firmware.git
1
0
Fork 0
Code Issues Releases Wiki Activity
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
7601 Commits
321 Branches
194 Tags
223 MiB
 
 
 
 
 
 
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '9e65c8c2ea'
${ noResults }
Go to file
Tomas Zorvan 9e65c8c2ea
common/defs: update minimal fee for Namecoin (#340) 		5 years ago
ci
…
common common/defs: update minimal fee for Namecoin (#340) 5 years ago
core core: add common page for success and warning 5 years ago
crypto
…
docs/git/hooks docs: set hook as executable 5 years ago
legacy webauthn: Add Binance to knownapps. Add Binance icon. 5 years ago
python core/reset: check three words 5 years ago
storage storage: fix incomatibility with new pytest 5 years ago
tools core/messages: don't generate unused messages 5 years ago
vendor
…
.clang-format
…
.gitignore
…
.gitlab-ci.yml
…
.gitmodules
…
.travis.yml
…
Makefile
…
Pipfile core/typing: add mypy 5 years ago
Pipfile.lock core/typing: add mypy 5 years ago
README-monorepo.md
…
README.md
…
SECURITY.md add SECURITY.md 5 years ago
create_monorepo.py
…
setup.cfg core/typing: add annotations 5 years ago
shell.nix nix: add coverage python package 5 years ago

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.