nft-marker-creator (Python)
Native Python package for creating NFT markers (.iset / .fset / .fset3)
for WebARKitLib / ARToolKit-based AR — a pybind11 wrapper around the same C++
core as the WASM tool, compiled natively (no WebAssembly). Ships both a
library and a command-line tool.
The generated markers are compatible with jsartoolkitNFT, ARnft, and AR.js.
Install
pip install nft-marker-creator
Prebuilt wheels are provided for Linux, macOS, and Windows across supported
Python versions, so no compiler or toolchain is required — pip just
downloads the right wheel. The only runtime dependency is
Pillow (installed automatically).
Building from source (contributors / unsupported platforms)
A source build compiles the native extension locally and needs: a C++17
compiler (clang recommended), CMake ≥ 3.18, and libjpeg + zlib
development headers, plus the WebARKitLib git submodule.
git clone --recurse-submodules https://github.com/webarkit/Nft-Marker-Creator-App
cd Nft-Marker-Creator-App
# Debian/Ubuntu: sudo apt install build-essential clang cmake libjpeg-dev zlib1g-dev
CC=clang CXX=clang++ pip install ./python
Usage
Command line
nft-marker-creator -i pinball.jpg -o output --threads 4
Prints the paths of the written marker files. Options:
| Option | Description | Default |
|---|---|---|
-i, --input |
Input image (jpg/jpeg/png) (required) | — |
-o, --output |
Output directory | current directory |
--dpi |
Override DPI | image metadata/150 |
--level |
Tracking extraction level (0–4) | 2 |
--leveli |
Initialization extraction level (0–3) | 1 |
--threads |
Worker threads | 1 |
Also runnable as python -m nft_marker_creator ....
Library
import nft_marker_creator as nmc
paths = nmc.create("pinball.jpg", output_dir="output", threads=4)
print(paths) # ['output/pinball.iset', 'output/pinball.fset', 'output/pinball.fset3']
create(image, output_dir=".", dpi=None, level=2, leveli=1, threads=1) returns
the list of written file paths and raises RuntimeError on failure (it never
terminates the host process). threads > 1 uses real OS threads; the output is
byte-identical regardless of thread count.
Notes
- Output files:
<name>.iset,<name>.fset,<name>.fset3. - Marker creation is memory-bandwidth-bound; threading speedup typically plateaus around 4 threads.
- This package is an additional, native distribution alongside the Node/WASM CLI in the same repository — not a replacement.
License
LGPL-3.0 (same as the parent project).
1 maintainer
Metadata
1 maintainer
Release files for nft-marker-creator 0.1.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 |
|---|---|---|---|---|
| nft_marker_creator-0.1.0.tar.gz | 36.7 kB | With provenance | Details for nft_marker_creator-0.1.0.tar.gz |
Built distributions (wheels)
Total release size: 4.6 MB
Release files / nft_marker_creator-0.1.0.tar.gz
| Download URL | nft_marker_creator-0.1.0.tar.gz |
|---|---|
| Size | 36.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
41a3b7fad5b5585fbd18f0d8326c2226374a8cfe117eda31fcbcb5d1ede7361f
|
|
BLAKE2b-256 checksum How to use checksums |
8bff4bbd2cbc2e34d9bd9b6ba2cb85b52ae46e00d593f59311972554df244752
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 Jul 4, 2026.
Transparency logRelease files / nft_marker_creator-0.1.0-cp313-cp313-win_amd64.whl
| Download URL | nft_marker_creator-0.1.0-cp313-cp313-win_amd64.whl |
|---|---|
| Size | 395.1 kB |
| Tags | CPython 3.13 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
198aab0d8f898005c0ecca6c6ad18c5b4abe89f5133f35877937876861a2478e
|
|
BLAKE2b-256 checksum How to use checksums |
76f84b78cb144b2de4b7b76f75256855f691264d2cc63401d0d8376b68a90b14
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 Jul 4, 2026.
Transparency logRelease files / nft_marker_creator-0.1.0-cp313-cp313-manylinux_2_28_x86_64.whl
| Download URL | nft_marker_creator-0.1.0-cp313-cp313-manylinux_2_28_x86_64.whl |
|---|---|
| Size | 371.8 kB |
| Tags | CPython 3.13 Linux glibc 2.28+ x86-64 |
|
SHA-256 checksum How to use checksums |
633587b16a94fcbf6dbfc64a44a6f9c37cb23ea71b755d4b962a520156294b86
|
|
BLAKE2b-256 checksum How to use checksums |
68c3221bb19b087cee0b53a14778b0efe47563014870a5564292c40c8f85b5b6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 Jul 4, 2026.
Transparency logRelease files / nft_marker_creator-0.1.0-cp312-cp312-win_amd64.whl
| Download URL | nft_marker_creator-0.1.0-cp312-cp312-win_amd64.whl |
|---|---|
| Size | 395.0 kB |
| Tags | CPython 3.12 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
281fc2b90794098a1c71c5fc69146242d0347572ab2d3b6f59cad2ea68e03292
|
|
BLAKE2b-256 checksum How to use checksums |
9ec9bcf875864510fdc353c3d561eca528a17aa4d82f8333e24a7f6f8874b4ee
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 Jul 4, 2026.
Transparency logRelease files / nft_marker_creator-0.1.0-cp312-cp312-manylinux_2_28_x86_64.whl
| Download URL | nft_marker_creator-0.1.0-cp312-cp312-manylinux_2_28_x86_64.whl |
|---|---|
| Size | 371.7 kB |
| Tags | CPython 3.12 Linux glibc 2.28+ x86-64 |
|
SHA-256 checksum How to use checksums |
4046e97d170cdbe19bc8722b37257c78a4145774bb91458e2bfd5c1200d28023
|
|
BLAKE2b-256 checksum How to use checksums |
560195ca76fec77cd80ba4d25bb57a69c6e840a4486c993b54cb3133393e7bbc
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 Jul 4, 2026.
Transparency logRelease files / nft_marker_creator-0.1.0-cp311-cp311-win_amd64.whl
| Download URL | nft_marker_creator-0.1.0-cp311-cp311-win_amd64.whl |
|---|---|
| Size | 393.6 kB |
| Tags | CPython 3.11 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
3f4f4810448f6eaf9d00af34cade8178966b80d7c43b581a8da15f9120fbcb49
|
|
BLAKE2b-256 checksum How to use checksums |
794d46af3c319123303aa40fca11f4d245aaef65fd4aaa754ab6af4d473eee25
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 Jul 4, 2026.
Transparency logRelease files / nft_marker_creator-0.1.0-cp311-cp311-manylinux_2_28_x86_64.whl
| Download URL | nft_marker_creator-0.1.0-cp311-cp311-manylinux_2_28_x86_64.whl |
|---|---|
| Size | 372.1 kB |
| Tags | CPython 3.11 Linux glibc 2.28+ x86-64 |
|
SHA-256 checksum How to use checksums |
0c357f326415e4d760b17d4cbb3022276765ec500ee39fe3761ad377650dfd4e
|
|
BLAKE2b-256 checksum How to use checksums |
330cd9980ecbfbb692b918ea013f7d8381931ecfd969bc28db2acd335653bbd5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 Jul 4, 2026.
Transparency logRelease files / nft_marker_creator-0.1.0-cp310-cp310-win_amd64.whl
| Download URL | nft_marker_creator-0.1.0-cp310-cp310-win_amd64.whl |
|---|---|
| Size | 392.9 kB |
| Tags | CPython 3.10 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
d07d95e56888be71e05e33aa96e28d3fbe52b6bdee7be25724e462cae3a5f01a
|
|
BLAKE2b-256 checksum How to use checksums |
c5983763c30927deec7dcf87651f8893f269c6a2f4d0e41fc57c421ed853caf9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 Jul 4, 2026.
Transparency logRelease files / nft_marker_creator-0.1.0-cp310-cp310-manylinux_2_28_x86_64.whl
| Download URL | nft_marker_creator-0.1.0-cp310-cp310-manylinux_2_28_x86_64.whl |
|---|---|
| Size | 370.1 kB |
| Tags | CPython 3.10 Linux glibc 2.28+ x86-64 |
|
SHA-256 checksum How to use checksums |
da08337eb7e6b0b78510577d3f79943956e515f9497b3d7c1e008eeb0b77dc55
|
|
BLAKE2b-256 checksum How to use checksums |
dfeb0e0987c3009530f690315094834e0def9eaabf4cac90780d4c3d7ad04c5f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 Jul 4, 2026.
Transparency logRelease files / nft_marker_creator-0.1.0-cp39-cp39-win_amd64.whl
| Download URL | nft_marker_creator-0.1.0-cp39-cp39-win_amd64.whl |
|---|---|
| Size | 393.1 kB |
| Tags | CPython 3.9 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
2a915ede2746b56a3037e34cd5ad9a7d82091ec511e7b4c190f06766210273eb
|
|
BLAKE2b-256 checksum How to use checksums |
697e8e5182c16c9f25c49402dcf61b123b7194119c4131c0749a0e1e2c38a4a4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 Jul 4, 2026.
Transparency logRelease files / nft_marker_creator-0.1.0-cp39-cp39-manylinux_2_28_x86_64.whl
| Download URL | nft_marker_creator-0.1.0-cp39-cp39-manylinux_2_28_x86_64.whl |
|---|---|
| Size | 370.2 kB |
| Tags | CPython 3.9 Linux glibc 2.28+ x86-64 |
|
SHA-256 checksum How to use checksums |
d98d4d6c23d33ffaf733bb3c4a52fa45c0a2f9cb55023e5dda53f145b65f0e72
|
|
BLAKE2b-256 checksum How to use checksums |
0645556d5dd02ec382bb7a796e5361200ecd4c60352c753268c8b265854d9306
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 Jul 4, 2026.
Transparency logRelease files / nft_marker_creator-0.1.0-cp38-cp38-win_amd64.whl
| Download URL | nft_marker_creator-0.1.0-cp38-cp38-win_amd64.whl |
|---|---|
| Size | 392.9 kB |
| Tags | CPython 3.8 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
5f423250b0bdbcb5fd21ec99b6690c651c1af6fbcf577f04366925b8041afae0
|
|
BLAKE2b-256 checksum How to use checksums |
79d689499d024e88cb3891820b828243ac082791bd18710429278155b02590fa
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 Jul 4, 2026.
Transparency logRelease files / nft_marker_creator-0.1.0-cp38-cp38-manylinux_2_28_x86_64.whl
| Download URL | nft_marker_creator-0.1.0-cp38-cp38-manylinux_2_28_x86_64.whl |
|---|---|
| Size | 370.1 kB |
| Tags | CPython 3.8 Linux glibc 2.28+ x86-64 |
|
SHA-256 checksum How to use checksums |
6729503370c1beb5ab0646bf9fe87b58edf1511b911cae2fd37ae66ecd273218
|
|
BLAKE2b-256 checksum How to use checksums |
45b15e3b9c25b40aa8940eb1aee37e465af68aa453c842eee9133c7d02495c58
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 Jul 4, 2026.
Transparency logSecurity for nft-marker-creator 0.1.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.
Full provenance
All 13 files in this release have been uploaded with provenance metadata.
Attestation for nft_marker_creator-0.1.0.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 Jul 4, 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.
