1
0
mirror of https://github.com/trezor/trezor-firmware.git synced 2024-10-18 05:49:11 +00:00
Go to file
2023-10-18 13:18:32 +02:00
.clusterfuzzlite
.github
ci
common
core
crypto feat(core): Integrate Optiga into PIN verification. 2023-09-27 17:17:09 +02:00
docs
legacy chore(python): use model names more consistently 2023-10-18 13:18:32 +02:00
python
rust
storage
tests fix(core/ui): wording in recovery flow 2023-10-18 12:04:52 +02:00
tools fix(tools): remove leading zero from "01st" in changelog dates 2023-10-06 10:49:29 +02:00
vendor
.clang-format
.editorconfig
.gitignore
.gitlab-ci.yml
.gitmodules
.yamllint.yml
build-docker.sh
CODEOWNERS chore(CODEOWNERS): remove me from some components 2021-10-17 10:45:14 +02:00
COMMITS.md
CONTRIBUTING.md
COPYING
create_monorepo.py
LICENSE.md
Makefile
poetry.lock
poetry.toml
pyproject.toml
README.md chore(readme): add link to trezor.io KB disclosure article 2023-01-09 10:45:31 +01:00
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.