fme-packager: FME Package Creator
fme-packager is a Python command-line tool for validating and creating FME Packages.
Give it the path to an FME Package directory, and it'll do some quick checks
and build an .fpkg file out of it.
The validations done by fme-packager will catch common mistakes in package development,
but is still very basic. The FME Packages it creates will be
validly formed according to the FME Packages Specification,
but whether the installed components function correctly within FME is not in its scope.
Install
Download the latest whl distribution from the releases page. Then install it:
$ pip install [fme-packager].whl
Once installed, the fme-packager command is available on your system.
fme-packager --help shows an overview of commands.
What it does
- Validate package.yml against the FME Packages Specification.
- Verifies that components listed in package.yml are present.
- Checks that transformer and format names are valid and well-formed.
- Verifies that the transformer version in the package.yml is included in the FMX/FMXJ.
- Verifies FMXJ schema compliance.
- Requires that Custom Transformers be Linked Always, declare Python 3 support, and authored with a sufficiently recent version of FME Workbench.
- Excludes components that are present in directories, but not listed in package.yml.
- Cleans and rebuilds wheels for Python packages that are subdirectories of
python/. - Copies wheels from
python/*/distintopython/. - Enforces required package icon dimensions.
These steps are done while copying files into a temporary build directory, so existing files are not modified.
Get started with a template
fme-packager init [template name] helps you get started with developing FME Packages by
using Cookiecutter templates.
Available templates:
transformer: Transformer template for FME Packages
These templates are not bundled with fme-packager.
Make an fpkg distribution
Call fme-packager pack with the path to your package directory (it contains package.yml):
$ fme-packager pack my-package
If everything went well, the fpkg will be in my-package/dist/.
Metadata
Release files for fme-packager 1.20.2
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 | |
|---|---|---|---|---|
| fme_packager-1.20.2.tar.gz | 58.9 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| fme_packager-1.20.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 108.7 kB
Release files / fme_packager-1.20.2.tar.gz
| Download URL | fme_packager-1.20.2.tar.gz |
|---|---|
| Size | 58.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
a13c292c8ec263603f161b4048e0736cd6c36919af1e979ada0dfec943cf1649
|
|
BLAKE2b-256 checksum How to use checksums |
f5469961febc98c0d259ec082bf3aa0d0f46e25d8bc4fbc4360059281d9a7446
|
| 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 Aug 11, 2026.
Transparency logRelease files / fme_packager-1.20.2-py3-none-any.whl
| Download URL | fme_packager-1.20.2-py3-none-any.whl |
|---|---|
| Size | 49.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
a096aea97320afb8f97b6ffd343e4ea1020d82760cfa81a959f477f3d1997774
|
|
BLAKE2b-256 checksum How to use checksums |
25b4ee3191f2b0f5e7f5b7ea2136de192001a1705e385b7da2cbe90c3b4e443e
|
| 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 Aug 11, 2026.
Transparency logSecurity for fme-packager 1.20.2
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 fme_packager-1.20.2.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 Aug 11, 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.