KiCad Library Manager (KiLM)
Professional command-line tool for managing KiCad libraries across projects and workstations.
Features
- Automatically detect KiCad configurations across different platforms (Windows, macOS, Linux)
- Add symbol and footprint libraries to KiCad from a centralized repository
- Set environment variables directly in KiCad configuration
- Pin favorite libraries for quick access in KiCad
- Create timestamped backups of configuration files
- Support for environment variables
- Dry-run mode to preview changes
- Compatible with KiCad 6.x and newer
- Project template management to standardize new designs
- Import vendor part ZIPs (SamacSys/Mouser, UltraLibrarian, SnapMagic) into your library
Quick Start
# Install (recommended)
pipx install kilm
# Verify installation
kilm --version
# Initialize a library
kilm init --name my-library --description "My KiCad components"
# Set up KiCad to use your libraries
kilm setup
# Check current configuration
kilm status
Complete Installation Guide - Multiple installation methods, verification steps, and troubleshooting.
Nix
Run without installing:
nix run github:barisgit/KiLM -- --version
Build, or drop into a dev shell:
nix build github:barisgit/KiLM # ./result/bin/kilm
nix develop # Python, deps, pytest, and uv for lint gates
Add to a NixOS / home-manager config via the overlay:
{
inputs.kilm.url = "github:barisgit/KiLM";
# in your config:
nixpkgs.overlays = [ inputs.kilm.overlays.default ];
environment.systemPackages = [ pkgs.kilm ]; # or home.packages
}
Documentation
| Guide | Description |
|---|---|
| Getting Started | Creator and consumer workflows with Git integration |
| Configuration | KiLM and KiCad configuration management |
| CLI Reference | Complete command documentation with examples |
| Development | Setup guide for contributors and development |
License
Contributing
Contributions are welcome. With uv, just, and pnpm installed:
git clone https://github.com/barisgit/KiLM.git
cd KiLM
just setup # locked dependencies and git hooks
just check # everything CI runs
See CONTRIBUTING.md for the pull request process and AGENTS.md for the layout and coding standards.
1 maintainer
Metadata
1 maintainer
Release files for kilm 0.6.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| kilm-0.6.0.tar.gz | 857.3 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| kilm-0.6.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 1.0 MB
Release files / kilm-0.6.0.tar.gz
| Download URL | kilm-0.6.0.tar.gz |
|---|---|
| Size | 857.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d26a27f0097f95211f7ca31ee8695a4898853b63324082b3b70f90b568d88ffb
|
|
BLAKE2b-256 checksum How to use checksums |
a7022416fbef88b5e0d5db46dd3d0b5d825abe508e0d3ea91327ff197d068c7a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 13, 2026.
Transparency logRelease files / kilm-0.6.0-py3-none-any.whl
| Download URL | kilm-0.6.0-py3-none-any.whl |
|---|---|
| Size | 159.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
7f0f0738f41eee2ed17b616421fc1791c6534713051e6217ab275925dbda8af1
|
|
BLAKE2b-256 checksum How to use checksums |
334ac16f7b30d595ca44f81ca83f70e1dacac88867d1342f5e77867aaa776d45
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 13, 2026.
Transparency log
