PicoForge

An open source commissioning tool for Pico FIDO security keys

Important

PicoForge is an independent, community-developed tool and is not affiliated with or endorsed by the official pico-fido project. This software does not share any code with the official closed-source pico-fido application.

Check application Installation Wiki for installation guide of the PicoForge app on your system.

About

PicoForge is a modern desktop application for configuring and managing Pico FIDO security keys. Built with Rust, Tauri, and Svelte, it provides an intuitive interface for:

Reading device information and firmware details
Configuring USB VID/PID and product names
Adjusting LED settings (GPIO, brightness, driver)
Managing security features (secure boot, firmware locking) (WIP)
Real-time system logging and diagnostics
Support for multiple hardware variants and vendors

Alpha Status: This application is currently under active development and in alpha stage. Users should expect bugs and are encouraged to report them. The app has been tested on Linux and Windows 10 with the official Raspberry Pi Pico2 & ESP32-S3 and, currently supports Pico FIDO firmware version 7.2 only.

Screenshots

Main Interface

Configuration Panel

Pin config

Other Config

Features

Device Configuration - Customize USB identifiers, LED behavior, and hardware settings
Security Management - Enable secure boot and firmware verification (experimental and WIP)
Real-time Monitoring - View flash usage, connection status, and system logs
Modern UI - Clean, responsive interface built with Svelte and shadcn-svelte
Multi-Vendor Support - Compatible with multiple hardware variants
Cross-Platform - Works on Windows, macOS, and Linux

Installation

Check the official PicoForge Wiki for installation info of the application.

Usage

Connect your smart card reader
Insert your Pico FIDO device
Launch PicoForge
Click Refresh button at top right corner to detect your key
Navigate through the sidebar to configure settings:
- Home - Device overview and quick actions
- Configuration - USB settings, LED options
- Security - Secure boot management (experimental)
- Logs - Real-time event monitoring
- About - Application information

Requirements

Development Requirements

To contribute to PicoForge, you'll need:

Node.js - JavaScript/TypeScript runtime
Deno - JavaScript/TypeScript runtime
Rust - System programming language (1.80+)
PC/SC Middleware:
- Linux: pcscd (usually pre-installed)
- macOS: Built-in
- Windows: Built-in

Building from Source

1. Clone the Repository

git clone https://github.com/librekeys/picoforge.git
cd picoforge

2. Install Dependencies

Using Deno (Recommended)

deno install

Using npm

npm install

3. Build the Application

Development Build

With Deno:

deno task tauri dev

With npm:

npm run tauri dev

Production Build

With Deno:

deno task tauri build

With npm:

npm run tauri build

The compiled binaries will be available in:

Linux: src-tauri/target/release/bundle/
macOS: src-tauri/target/release/bundle/dmg/
Windows: src-tauri/target/release/bundle/

Building and Development with Nix

Nix provides developers with a complete and consistent development environment.

You can use Nix to build and develop picoforge painlessly.

1. Install Nix

Follow the Installation Guide and NixOS Wiki to install Nix and enable Flakes.

2. Build & Run

a. with Flakes

You can build and run PicoForge with a single command:

nix run github:librekeys/picoforge

Or simply build it and link to the current directory:

nix build github:librekeys/picoforge

b. without Flakes

Download the package definition:

curl -LO https://raw.githubusercontent.com/librekeys/picoforge/main/package.nix

Run the following command in the directory containing package.nix:

nix-build -E 'with import <nixpkgs> {}; callPackage ./package.nix { }'

The compiled binary will be available at: result/bin/picoforge

3. Develop

You can enter a developement environement with all the required dependencies.

a. with Flakes

nix develop github:librekeys/picoforge

b. without Flakes

You can use the shell.nix file that is at the root of the repository by running:

nix-shell

Then you can build from source and run the application with:

deno task tauri dev

Project Structure

picoforge/
├── src/                      # Svelte frontend
│   ├── lib/                  # Reusable components & utilities
│   │   ├── components/       # UI components
│   │   ├── device/           # Device-related logic
│   │   ├── hooks/            # Custom Svelte hooks
│   │   ├── layout/           # Layout components
│   │   ├── services/         # Service layer
│   │   ├── state/            # State management
│   │   ├── utils.ts          # Utility functions
│   │   └── views/            # View components
│   ├── routes/               # SvelteKit pages
│   │   ├── +layout.svelte    # Root layout
│   │   ├── +layout.ts        # Layout configuration
│   │   └── +page.svelte      # Home page
│   ├── app.css               # Global styles
│   └── app.html              # HTML template
├── src-tauri/                # Rust backend
│   ├── src/                  # Rust source code
│   │   ├── fido/             # FIDO device logic
│   │   ├── rescue/           # Rescue mode functionality
│   │   ├── error.rs          # Error handling
│   │   ├── io.rs             # I/O operations
│   │   ├── lib.rs            # Tauri commands & PC/SC logic
│   │   ├── logging.rs        # Logging utilities
│   │   ├── main.rs           # Entry point
│   │   └── types.rs          # Type definitions
│   ├── icons/                # Application icons
│   ├── capabilities/         # Tauri permissions
│   │   └── default.json      # Default capabilities
│   ├── Cargo.toml            # Rust dependencies
│   ├── Cargo.lock            # Rust lock file
│   ├── tauri.conf.json       # Tauri configuration
│   ├── build.rs              # Build script
│   └── rustfmt.toml          # Rust formatting config
├── static/                   # Static assets
│   ├── build-configure-symbolic.svg
│   ├── favicon.png
│   ├── in.suyogtandel.picoforge.svg
│   ├── svelte.svg
│   ├── tauri.svg
│   └── vite.svg
├── data/                     # Application data
│   ├── in.suyogtandel.picoforge.desktop
│   └── screenshots/          # Screenshots
├── node_modules/             # Deno node compatibility modules
├── components.json           # shadcn-svelte config
├── package.json              # Node package manifest
├── package-lock.json         # npm lock file
├── deno.json                 # Deno configuration
├── deno.lock                 # Deno lock file
├── svelte.config.js          # SvelteKit configuration
├── vite.config.js            # Vite bundler config
├── tsconfig.json             # TypeScript configuration
├── biome.json                # Biome configuration
├── CREDITS.md                # Credits
└── LICENSE                   # AGPL-3.0 license

Contributing

Contributions are welcome (REALLY NEEDED, PLEASE HELP ME)! Please follow these steps:

Fork the repository
Create a feature branch (git checkout -b feature/amazing-feature)
Commit your changes (git commit -m 'Add amazing feature')
Push to the branch (git push origin feature/amazing-feature)
Open a Pull Request

Development Guidelines

Follow Rust and TypeScript best practices
Use deno fmt to format the frontend code
Write clear commit messages
Update documentation for new features
Test on multiple platforms when possible

License

This project is licensed under the GNU Affero General Public License v3.0 (AGPL-3.0-only).

See LICENSE for full details.

Maintainers

Suyog Tandel (@lockedmutex)

Support

Discord: Join our Discord server for community support and interaction
Issues: GitHub Issues
Discussions: GitHub Discussions

Disclaimer

Warning

PicoForge is experimental software and still in the Beta stage! The app does contain bugs and is not secure by any means.

It does not support all the features exposed by the pico-fido firmware and pico-hsm.

Caution

USB VID/PID Notice: The vendor presets provided in this software include USB Vendor IDs (VID) and Product IDs (PID) that are the intellectual property of their respective owners. These identifiers are included for testing and educational purposes only. You are NOT authorized to distribute or commercially market devices using VID/PID combinations you do not own or license. Commercial distribution requires obtaining your own VID from the USB Implementers Forum (usb.org) and complying with all applicable trademark and certification requirements. Unauthorized use may violate USB-IF policies and intellectual property laws. The PicoForge developers assume no liability for misuse of USB identifiers.

Made with ❤️ by the LibreKeys community

Name		Name	Last commit message	Last commit date
Latest commit History 128 Commits
.github/workflows		.github/workflows
.tito		.tito
data		data
docs		docs
src-tauri		src-tauri
src		src
static		static
.envrc		.envrc
.gitignore		.gitignore
CREDITS.md		CREDITS.md
LICENSE		LICENSE
README.md		README.md
biome.json		biome.json
components.json		components.json
deno.json		deno.json
deno.lock		deno.lock
flake.lock		flake.lock
flake.nix		flake.nix
package-lock.json		package-lock.json
package.json		package.json
package.nix		package.nix
picoforge.spec		picoforge.spec
shell.nix		shell.nix
svelte.config.js		svelte.config.js
tsconfig.json		tsconfig.json
vite.config.js		vite.config.js

License

librekeys/picoforge

Folders and files

Latest commit

History

Repository files navigation

PicoForge

About

Screenshots

Main Interface

Configuration Panel

Pin config

Other Config

Features

Installation

Usage

Requirements

Development Requirements

Building from Source

1. Clone the Repository

2. Install Dependencies

Using Deno (Recommended)

Using npm

3. Build the Application

Development Build

Production Build

Building and Development with Nix

1. Install Nix

2. Build & Run

a. with Flakes

b. without Flakes

3. Develop

a. with Flakes

b. without Flakes

Project Structure

Contributing

Development Guidelines

License

Maintainers

Support

Disclaimer

About

Topics

Resources

License

Uh oh!

Stars

Watchers

Forks

Releases 10

Contributors 5

Languages