Chriesibaum's JEP106 Tool Box
A python library and toolbox that parses the Standard Manufacturer’s Identification Code (JEP106) and converts the content into a machine-readable file like a CSV or JSON.
The data can also be easily used in Python projects by utilizing the Python class Jep106Db()
It is entirely written in Python.
Installation
pip install -e .
Example
from cb_jep106 import Jep106Db
jep106 = Jep106Db()
print(jep106.get_manufacturer(0x001))
print(jep106.get_manufacturer(0x020))
print(jep106.get_manufacturer(0x23b))
This outputs the following text:
AMD
STMicroelectronics
ARM Ltd
CLI Usage
cb_jep106_converter -i <JEP106xx.pdf> -j <JEP106xx.json>
cb_jep106_converter --help
usage: cb_jep106_converter [-h] [-i <JEP106xx.pdf>] [-c <csv file>] [-j <json file>]
Decode the Standard Manufacturer’s Identification Code PDF file (JEP106xx.pdf)
and generate machine readable output like a CSV or JSON file.
Note:
As the JEP106xx.pdf is not free to use, it is not included in the repository but
can be used by downloading the JEP106xx.pdf from JEDEC and running this script locally.
At the time of writing, the actual JEP106BN.pdf can be found at
https://www.jedec.org/standards-documents/docs/jep-106ab.
Finally, have fun with the JEP106 data! :)
options:
-h, --help show this help message and exit
-i <JEP106xx.pdf>, --pdf <JEP106xx.pdf>
Path to input JEP106 PDF file (default: ./JEP106/JEP106BN.pdf)
-c <csv file>, --csv <csv file>
Path to output CSV file
-j <json file>, --json <json file>
Path to output JSON file
At least one output must be provided: `-c/--csv` or `-j/--json`.
Metadata
Release files for cb-jep106 0.1.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| cb_jep106-0.1.1.tar.gz | 379.9 kB | With provenance | Details for cb_jep106-0.1.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| cb_jep106-0.1.1-py3-none-any.whl | Python 3 | none | any | Details for cb_jep106-0.1.1-py3-none-any.whl |
Total release size: 429.9 kB
Release files / cb_jep106-0.1.1.tar.gz
| Download URL | cb_jep106-0.1.1.tar.gz |
|---|---|
| Size | 379.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
6a17f07be50fb0289416b5908092c11c1d7600d19696d419ecaaf798bf6e2118
|
|
BLAKE2b-256 checksum How to use checksums |
09a15422e0c7285860b662203d4e07bcac26305e4a941d560e198adfa64fa7bd
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
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 Mar 27, 2026.
Transparency logRelease files / cb_jep106-0.1.1-py3-none-any.whl
| Download URL | cb_jep106-0.1.1-py3-none-any.whl |
|---|---|
| Size | 50.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
2c940fb4fd7ecef6dbd3fc161ad8dea2920e5463ba370613d22853b08405499c
|
|
BLAKE2b-256 checksum How to use checksums |
b98f804ed5067bed74f431d98d69f280b93cd3c7adb9017df3aaed9b2c97a40d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
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 Mar 27, 2026.
Transparency logSecurity for cb-jep106 0.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.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for cb_jep106-0.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 Mar 27, 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.