Warning
This repository has been inactive for a good amount of time so it is archived until developement work resumes
A Web app to visualise your TUF data.
This software is in very early stage for now, use at your own risk! And read the "security" section
- human-friendly display of TUF JSON files
- visualise minified JSON files in indented multi-line form
- collects and displays info about keys
- JSON diff between arbitrary commits, with TUF-specific heuristics for improved diffing
Do not use TUF Explorer to visualise TUF data that you don't already trust.
TUF Exporer does not do any sort of validation of the TUF data for now. For instance it does not check any of the signatures.
Also, for now an attacker could trigger an XSS attack by making you visualise malicious TUF documents. This is being tracked by issue #1.
As a container:
docker build --tag tuf-explorer .
As a NodeJS app:
npm install
The app will need three env variables: TUF_EXPLORER_ROOT_DIR
, TUF_EXPLORER_REPOS_ROOT_DIR_SUFFIX
and TUF_EXPLORER_REPOS_KEY_INFO_DIR_SUFFIX
. There is an optional variable TUF_EXPLORER_COMMON_ROOTS_PREFIX
.
- the root of the git repository must be at
root_dir
(used for thediff
feature) - the app will look for TUF repositories in
[root_dir]/[common_prefix]/[root_dir_suffix]
- the app will look for key info files in
[root_dir]/[common_prefix]/[key_info_dir_suffix]
To run a NodeJS App:
npm run dev
To run as a container:
docker run \
-p 127.0.0.1:3000:3000 \
--env TUF_EXPLORER_REPOS_KEY_INFO_DIR_SUFFIX=<to fill> \
--env TUF_EXPLORER_REPOS_ROOT_DIR_SUFFIX=<to fill> \
-v <path to your git repo>:/etc/tuf-explorer:ro \
tuf-explorer
For instance if you have a git repository located at $HOME/code/my-repo
which contains TUF repositories at path data/tuf
and key info files at path data/helper
you could do:
docker run \
-p 127.0.0.1:3000:3000 \
--env TUF_EXPLORER_REPOS_KEY_INFO_DIR_SUFFIX=data/helper \
--env TUF_EXPLORER_REPOS_ROOT_DIR_SUFFIX=data/tuf \
-v $HOME/code/my-repo/:/etc/tuf-explorer/data:ro \
tuf-explorer
Note the :ro
suffix in the volume mount (TUF Explorer does not need to write to this volume).
Also note that you can use a different port than 3000 on your host.