dirt-bike-graphics-fitment
Which dirt bikes share the same plastics, and so can run the same graphics kit. 175 model years (76 models, 11 brands) grouped under 17 reference bikes: motocross, enduro and electric.
Use it to answer "will a kit for my 2024 YZ250F fit a 2025 YZ450F?" in a parts shop, a decal store or a bike forum bot.
Install
pip install dirt-bike-graphics-fitment
Usage
from dirt_bike_graphics_fitment import BIKES, find_kit, same_kit, shared_fits
find_kit("CRF250R", 2026)["id"]
# 'honda-crf450r-2025'
shared_fits("YZ250F", 2025)
# ['2023 YZ450F', '2024 YZ450F', ..., '2026 YZ250FX']
same_kit(("CRF450R", 2025), ("CRF250R", 2026))
# True
len(BIKES)
# 17
Model names are matched loosely: yz250f, YZ 250 F and YZ250F are the same. The year is optional.
Data
Each entry in bikes (also in fitment.json):
| Field | Example |
|---|---|
id |
honda-crf450r-2025 |
brand |
Honda |
model |
CRF450R |
reference_year |
2025 |
category |
MX, Enduro or Electric |
fits |
["2025 CRF450R", "2026 CRF450R", "2025 CRF250R", "2026 CRF250R"] |
Brands: Beta, Ducati, GasGas, Honda, Husqvarna, Kawasaki, KTM, Stark, Suzuki, Triumph, Yamaha.
Not covered: aftermarket plastics (Acerbis, Polisport, UFO), which usually but not always follow the stock shape, and small mid-year changes.
Design a kit for these bikes
The data comes from Custom Dirt Bike Graphics, an AI dirt bike graphics generator. Describe the design you want, get a full kit laid out for your bike, then edit every panel online. Open the dirt bike graphics designer
Contributing
Found a mistake or a missing fitment? Open an issue with the model, the years and your source.
License
MIT
Metadata
Release files for dirt-bike-graphics-fitment 1.0.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 | Provenance | Actions |
|---|---|---|---|---|
| dirt_bike_graphics_fitment-1.0.0.tar.gz | 4.6 kB | Without provenance | Details for dirt_bike_graphics_fitment-1.0.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| dirt_bike_graphics_fitment-1.0.0-py3-none-any.whl | Python 3 | none | any | Details for dirt_bike_graphics_fitment-1.0.0-py3-none-any.whl |
Total release size: 10.5 kB
Release files / dirt_bike_graphics_fitment-1.0.0.tar.gz
| Download URL | dirt_bike_graphics_fitment-1.0.0.tar.gz |
|---|---|
| Size | 4.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
69a9f4a23a6eafdb8fb7ca3ffe0b2ed6cf8d02e12d90f2354cfb51874c9cc75c
|
|
BLAKE2b-256 checksum How to use checksums |
86bbc2d6ae23e98289c2a495b20c3129ef35410732df3bd604fd0f14c6b8c563
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
stdlib-pypi-uploader/1.0
|
Release files / dirt_bike_graphics_fitment-1.0.0-py3-none-any.whl
| Download URL | dirt_bike_graphics_fitment-1.0.0-py3-none-any.whl |
|---|---|
| Size | 5.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
52b7c5390f1fb66adb4908333b632a548ed4f35340b54bf4cfd4c30723b58582
|
|
BLAKE2b-256 checksum How to use checksums |
d7351642b3dfb3ddd3e1f90b9d83c5040073e2c7c37dd8944243c0df79bf58e6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
stdlib-pypi-uploader/1.0
|
Security for dirt-bike-graphics-fitment 1.0.0
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.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A 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.