1
0
mirror of https://github.com/trezor/trezor-firmware.git synced 2024-10-18 22:09:07 +00:00
Go to file
2023-08-16 12:47:14 +02:00
.clusterfuzzlite
.github
ci
common
core feat: toiftool 2023-08-16 12:47:14 +02:00
crypto
docs
legacy chore(common): remove MUE support 2023-08-16 10:31:50 +02:00
python feat: toiftool 2023-08-16 12:47:14 +02:00
rust
storage
tests feat(tests): notify about failed tests when updating fixtures from CI 2023-08-09 16:07:27 +02:00
tools
vendor
.clang-format
.editorconfig
.gitignore
.gitlab-ci.yml
.gitmodules
.yamllint.yml
build-docker.sh build: differentiate between models for prodtest build 2023-06-14 12:23:03 +02:00
CODEOWNERS
COMMITS.md
CONTRIBUTING.md
COPYING
create_monorepo.py
LICENSE.md
Makefile
poetry.lock feat: toiftool 2023-08-16 12:47:14 +02:00
poetry.toml build(poetry): use new (parallel) installer 2022-11-08 12:21:46 +01:00
pyproject.toml feat: toiftool 2023-08-16 12:47:14 +02:00
README.md
SECURITY.md
setup.cfg
shell.nix

Trezor Firmware

img

Repository Structure

  • ci: Gitlab CI configuration files
  • common/defs: JSON coin definitions and support tables
  • common/protob: Common protobuf definitions for the Trezor protocol
  • common/tools: Tools for managing coin definitions and related data
  • core: Trezor Core, firmware implementation for Trezor T
  • crypto: Stand-alone cryptography library used by both Trezor Core and the Trezor One firmware
  • docs: Assorted documentation
  • legacy: Trezor One firmware implementation
  • python: Python client library and the trezorctl command
  • storage: NORCOW storage implementation used by both Trezor Core and the Trezor One firmware
  • tests: Firmware unit test suite
  • tools: Miscellaneous build and helper scripts
  • vendor: Submodules for external dependencies

Contribute

See CONTRIBUTING.md.

Using Conventional Commits is strongly recommended and might be enforced in future.

Also please have a look at the docs, either in the docs folder or at docs.trezor.io before contributing. The misc chapter should be read in particular because it contains some useful assorted knowledge.

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.

Documentation

See the docs folder or visit docs.trezor.io.