1
0
mirror of https://github.com/trezor/trezor-firmware.git synced 2024-12-22 06:18:07 +00:00
Go to file
2019-08-23 12:48:23 +02:00
ci ci: use explicit artifacts (don't use untracked: true) 2019-08-22 17:47:36 +02:00
common common/defs: add Umbru (#433) 2019-08-23 11:59:30 +02:00
core core: fix style 2019-08-23 12:35:17 +02:00
crypto docs: switch http to https in links (#419) 2019-08-16 17:28:15 +02:00
docs/git/hooks git/hooks: do not suppress output 2019-08-02 10:39:55 +02:00
legacy tests: make path to tested binary configurable 2019-08-22 17:47:36 +02:00
python python: make gen_check fail if coins.json are outdated 2019-08-23 12:48:23 +02:00
storage storage: explicitly reseed in PRNG tests 2019-08-12 12:57:25 +02:00
tests tests: add one more altcoin marker 2019-08-22 19:20:14 +02:00
tools tools/csv: modify weight 2019-08-21 16:09:53 +02:00
vendor core/secp256k1-zkp: use ARM assembly for field operations (#176) 2019-05-25 11:42:13 +02:00
.clang-format core+legacy: rework code styling checks 2019-04-18 17:40:55 +02:00
.gitignore ci: improve pipenv caching 2019-05-24 09:18:00 +02:00
.gitlab-ci.yml ci: split jobs based on stage not project 2019-08-19 14:47:12 +02:00
.gitmodules submodules: remove secp256k1-zkp's branch name because it will rotate 2019-06-04 08:21:42 +02:00
.travis.yml ci: use pipenv sync 2019-08-12 12:57:25 +02:00
create_monorepo.py monorepo: add notes and creation tool 2019-04-15 19:16:04 +02:00
Makefile make: run flake8 during style check as well 2019-08-06 10:08:23 +02:00
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 fix link in readme 2019-04-29 19:11:44 +02:00
README.md README: add note on CI 2019-05-23 13:19:44 +02:00
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 nix: add coverage python package 2019-06-26 22:25:04 +02:00

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.