quiddity
Rust-built STEP manufacturing feature recognition for CPython 3.11+, with no Python runtime dependencies. This replaces Python quiddity 0.3.11 with a new file-based API.
import json, quiddity
result = json.loads(quiddity.recognise("part.step"))
features = json.loads(quiddity.evidence("part.step"))["features"]
See the API and migration guide.
The quiddity console script and python -m quiddity run the Rust CLI.
1 maintainer
Metadata
1 maintainer
Release files for quiddity 0.4.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 | Actions |
|---|---|---|---|---|
| quiddity-0.4.2.tar.gz | 1.4 MB | With provenance | Details for quiddity-0.4.2.tar.gz |
Built distributions (wheels)
| File | Actions Reset | |||
|---|---|---|---|---|
| quiddity-0.4.2-cp311-abi3-win_amd64.whl | CPython 3.11 | abi3 | Windows x86-64 | Details for quiddity-0.4.2-cp311-abi3-win_amd64.whl |
| quiddity-0.4.2-cp311-abi3-manylinux_2_28_x86_64.whl | CPython 3.11 | abi3 | Linux glibc 2.28+ x86-64 | Details for quiddity-0.4.2-cp311-abi3-manylinux_2_28_x86_64.whl |
| quiddity-0.4.2-cp311-abi3-manylinux_2_28_aarch64.whl | CPython 3.11 | abi3 | Linux glibc 2.28+ ARM64 | Details for quiddity-0.4.2-cp311-abi3-manylinux_2_28_aarch64.whl |
| quiddity-0.4.2-cp311-abi3-macosx_11_0_arm64.whl | CPython 3.11 | abi3 | macOS 11.0+ ARM64 | Details for quiddity-0.4.2-cp311-abi3-macosx_11_0_arm64.whl |
| quiddity-0.4.2-cp311-abi3-macosx_10_12_x86_64.whl | CPython 3.11 | abi3 | macOS 10.12+ x86-64 | Details for quiddity-0.4.2-cp311-abi3-macosx_10_12_x86_64.whl |
Total release size: 37.3 MB
Release files / quiddity-0.4.2.tar.gz
| Download URL | quiddity-0.4.2.tar.gz |
|---|---|
| Size | 1.4 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
0f1ad9fcab0bea3bfa1b7a7735912b5c09d53e9f60d8c1ef0252a444ed050d5e
|
|
BLAKE2b-256 checksum How to use checksums |
34e6a66e8093f0b72be4e81e60a1dccbfe55da4501bce8b4bf9e9ea65f1b727f
|
| 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 1, 2026.
Transparency logRelease files / quiddity-0.4.2-cp311-abi3-win_amd64.whl
| Download URL | quiddity-0.4.2-cp311-abi3-win_amd64.whl |
|---|---|
| Size | 7.6 MB |
| Tags | CPython 3.11 Windows x86-64 abi3 |
|
SHA-256 checksum How to use checksums |
0dfa1478073d227c5d0a27a044ad920aff44d55b71b6963416956c2c5531eda6
|
|
BLAKE2b-256 checksum How to use checksums |
e80d4a7176ba60a2e0a23934514608de8e5a81987b81f29f5a4516a8a3170622
|
| 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 1, 2026.
Transparency logRelease files / quiddity-0.4.2-cp311-abi3-manylinux_2_28_x86_64.whl
| Download URL | quiddity-0.4.2-cp311-abi3-manylinux_2_28_x86_64.whl |
|---|---|
| Size | 7.5 MB |
| Tags | CPython 3.11 Linux glibc 2.28+ x86-64 abi3 |
|
SHA-256 checksum How to use checksums |
d0f74e4e49858eee5826275cb21d79eb411d716b14874213528e7716b564f547
|
|
BLAKE2b-256 checksum How to use checksums |
dc5b52e964e3f237af2bb0c258bb13c6b1eb59eb830699ff3e60e93c2ec7be1f
|
| 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 1, 2026.
Transparency logRelease files / quiddity-0.4.2-cp311-abi3-manylinux_2_28_aarch64.whl
| Download URL | quiddity-0.4.2-cp311-abi3-manylinux_2_28_aarch64.whl |
|---|---|
| Size | 6.9 MB |
| Tags | CPython 3.11 Linux glibc 2.28+ ARM64 abi3 |
|
SHA-256 checksum How to use checksums |
8fe0e35536f106c2f25325c47d5e320fe6a4dbd0a69abbd04feb7b558c0bf9c5
|
|
BLAKE2b-256 checksum How to use checksums |
3fb7693ea506c8fbec88e8d63d12e2d878d20a274867343369491e4213c51d55
|
| 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 1, 2026.
Transparency logRelease files / quiddity-0.4.2-cp311-abi3-macosx_11_0_arm64.whl
| Download URL | quiddity-0.4.2-cp311-abi3-macosx_11_0_arm64.whl |
|---|---|
| Size | 6.6 MB |
| Tags | CPython 3.11 abi3 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
0ecaf3eb8b2c3e11be9d25e4f6659e3de85d629e6b7ef0cffb9a617224066e76
|
|
BLAKE2b-256 checksum How to use checksums |
bf1ddb61a12780ea4c0959036ab3c60054e8502c121c4bca772b0e7bfb5c43cb
|
| 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 1, 2026.
Transparency logRelease files / quiddity-0.4.2-cp311-abi3-macosx_10_12_x86_64.whl
| Download URL | quiddity-0.4.2-cp311-abi3-macosx_10_12_x86_64.whl |
|---|---|
| Size | 7.2 MB |
| Tags | CPython 3.11 abi3 macOS 10.12+ x86-64 |
|
SHA-256 checksum How to use checksums |
987a4fb427de9cc187d748a8859c176ca6d2b22ea0ec8d212a5978425224e119
|
|
BLAKE2b-256 checksum How to use checksums |
db80096ca703d54613b58d70c069d62988f628c3a4d869c2756711f6ff89c9b5
|
| 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 1, 2026.
Transparency logSecurity for quiddity 0.4.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 6 files in this release have been uploaded with provenance metadata.
Attestation for quiddity-0.4.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 Nov 1, 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.
