The repository or configuration that created this release differ from a previous release. View details.
Windows automator and database tools for Mixed In Key 11.
Installation
pip install mik-automator
Windows only, Python 3.11+.
If you installed it from GitHub as mixed-in-key-automator, uninstall that first (pip uninstall mixed-in-key-automator): both install the mik_automator package, so keeping both leaves them overwriting each other's files.
Usage
mik_automator
Opens Mixed In Key (or connects to it if it's already open), adds a folder, waits for the analysis to finish, then closes it.
from mik_automator import mik_automator
mik_automator.run(r"C:\Users\me\Music\DJ Tracks")
It knows the analysis is done once Mixed In Key's database stops changing and the window closes without asking to confirm.
mik_db
Reads and edits Mixed In Key's database (MIKStore.db) directly.
rename_file(src, dest, names=None): points a song at its renamed file, so it keeps its analysis.remove_files(filepaths)andremove_missing_files(): remove songs, so they're analyzed again when added, or because their file is gone.get_song_files()andget_files_missing_from_db(dir): read-only, safe while Mixed In Key is running.
Run python -m mik_automator.mik_db to remove the songs whose files no longer exist.
Development
python -m venv .venv
source .venv/Scripts/activate
pip install -e ".[dev]"
Type check with pyright, and lint and format with ruff check --fix . then ruff format .. CI checks all three on pull requests.
License
Metadata
Release files for mik-automator 1.1.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Change of provenance
The repository or configuration that created these release files differ from that of a previous release.
We recommend inspecting the repository and configuration before proceeding. View details.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| mik_automator-1.1.1.tar.gz | 8.5 kB | With provenance | Details for mik_automator-1.1.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| mik_automator-1.1.1-py3-none-any.whl | Python 3 | none | any | Details for mik_automator-1.1.1-py3-none-any.whl |
Total release size: 16.2 kB
Release files / mik_automator-1.1.1.tar.gz
Change of provenance
This file belongs to a release with changed provenance: the repository or configuration that created the release files differ from that of a previous release.
We recommend inspecting the repository and configuration before proceeding. View details.
| Download URL | mik_automator-1.1.1.tar.gz |
|---|---|
| Size | 8.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e0813a37fd0dc4e2f8c1dc48a84f10c180d68908e86c3ca0768b761e226ade3b
|
|
BLAKE2b-256 checksum How to use checksums |
65bc62f0b87539c0933897f62b67a504b654353defe877f5161be8d3f4daeede
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Nov 17, 2026.
Transparency logRelease files / mik_automator-1.1.1-py3-none-any.whl
Change of provenance
This file belongs to a release with changed provenance: the repository or configuration that created the release files differ from that of a previous release.
We recommend inspecting the repository and configuration before proceeding. View details.
| Download URL | mik_automator-1.1.1-py3-none-any.whl |
|---|---|
| Size | 7.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
3e82961475192a19645185bf76e13fefccd03d28541c1515f7a929732950462a
|
|
BLAKE2b-256 checksum How to use checksums |
bcf95155bf8b9bced99ab7f6a7e69806df066486b7334cfb5b62e93e2e0d01a6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Nov 17, 2026.
Transparency logSecurity for mik-automator 1.1.1
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.
Change of provenance
The configuration that created this release differs from a previous release.
While this could reflect a routine change by the project maintainers, it may also indicate that the release files have been compromised.
Attestation for mik_automator-1.1.1.tar.gz
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 Nov 17, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.