introspection-recipe-check for Python
Native Python bindings for the pure, I/O-free
introspection-recipe-check validation engine.
from introspection_recipe_check import check_recipe_files
report = check_recipe_files(
{
"files": [
{
"path": "package.json",
"content": '{"name":"demo","pi":{}}',
}
]
}
)
The binding performs no filesystem I/O. Paths are relative to the Recipe root,
and missing content means the host supplied file identity without source
text.
list_recipe_suggestions(snapshot) returns the same snapshot's suggestions:
the prompt templates marked suggest: true, in file order, as Suggestion
values (name, description, argument_hint, text and placeholders). It
reads them exactly as listRecipeSuggestions in @introspection-ai/recipes
does, so a host can offer them (as chat chips, say) without starting Pi.
1 maintainer
Metadata
1 maintainer
Release files for introspection-recipe-check 0.18.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 |
|---|---|---|---|---|
| introspection_recipe_check-0.18.0.tar.gz | 133.1 kB | With provenance | Details for introspection_recipe_check-0.18.0.tar.gz |
Built distributions (wheels)
Total release size: 9.4 MB
Release files / introspection_recipe_check-0.18.0.tar.gz
| Download URL | introspection_recipe_check-0.18.0.tar.gz |
|---|---|
| Size | 133.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
a3931b5e63cb57101d9deecefb0cd53db604e3a604a726a0403d3205827b059e
|
|
BLAKE2b-256 checksum How to use checksums |
ee7f589bcb36372bba61fd7a25de20a4ce70d643a249c54eaed246914085e6f9
|
| 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 4, 2026.
Transparency logRelease files / introspection_recipe_check-0.18.0-cp310-abi3-win_amd64.whl
| Download URL | introspection_recipe_check-0.18.0-cp310-abi3-win_amd64.whl |
|---|---|
| Size | 1.9 MB |
| Tags | CPython 3.10 Windows x86-64 abi3 |
|
SHA-256 checksum How to use checksums |
9779c30f83ab30125bab1dcc538e407e1104b84bb41aed8deae0ab6e15c6490a
|
|
BLAKE2b-256 checksum How to use checksums |
3bca049d578c886a97e3119e25dee3980907c112e42024b9603c18e5703ab16c
|
| 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 4, 2026.
Transparency logRelease files / introspection_recipe_check-0.18.0-cp310-abi3-manylinux_2_28_x86_64.whl
| Download URL | introspection_recipe_check-0.18.0-cp310-abi3-manylinux_2_28_x86_64.whl |
|---|---|
| Size | 2.0 MB |
| Tags | CPython 3.10 Linux glibc 2.28+ x86-64 abi3 |
|
SHA-256 checksum How to use checksums |
d23c8cbccf3baf866cc9412b4cc882a8cf737710c360f8a6ff0f4b813440336d
|
|
BLAKE2b-256 checksum How to use checksums |
cb51d74408c59bcd902f600d8f520003cb3396b243786a3fcb7d400442fb126e
|
| 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 4, 2026.
Transparency logRelease files / introspection_recipe_check-0.18.0-cp310-abi3-manylinux_2_28_aarch64.whl
| Download URL | introspection_recipe_check-0.18.0-cp310-abi3-manylinux_2_28_aarch64.whl |
|---|---|
| Size | 1.8 MB |
| Tags | CPython 3.10 Linux glibc 2.28+ ARM64 abi3 |
|
SHA-256 checksum How to use checksums |
49bd7ae6c8bca477200a6ba267f3f56955b3b12dfb7ad17e0cfedc12a2ea847c
|
|
BLAKE2b-256 checksum How to use checksums |
9fc3f99af9d1e7e6a0408158351d00666b3a125376a38c75ad8367a4f82a21b7
|
| 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 4, 2026.
Transparency logRelease files / introspection_recipe_check-0.18.0-cp310-abi3-macosx_11_0_arm64.whl
| Download URL | introspection_recipe_check-0.18.0-cp310-abi3-macosx_11_0_arm64.whl |
|---|---|
| Size | 1.7 MB |
| Tags | CPython 3.10 abi3 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
16af7e612c57cdffabd7b714e09def9f5de26895b51d3259dd705845cb1129b8
|
|
BLAKE2b-256 checksum How to use checksums |
bef540aecf4bd059e0a9e65873025ae8b05476542b859b2ea1fa4a0a3ee11e20
|
| 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 4, 2026.
Transparency logRelease files / introspection_recipe_check-0.18.0-cp310-abi3-macosx_10_12_x86_64.whl
| Download URL | introspection_recipe_check-0.18.0-cp310-abi3-macosx_10_12_x86_64.whl |
|---|---|
| Size | 1.8 MB |
| Tags | CPython 3.10 abi3 macOS 10.12+ x86-64 |
|
SHA-256 checksum How to use checksums |
06655073f418defdc888a26dacad3fbbd8ad4c6f6acdd8380df2fc1da8ebe3f3
|
|
BLAKE2b-256 checksum How to use checksums |
28a295cd34267508c7c6db09f98c0dda88255a4e6460f59e604d3e831112328e
|
| 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 4, 2026.
Transparency logSecurity for introspection-recipe-check 0.18.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 6 files in this release have been uploaded with provenance metadata.
Attestation for introspection_recipe_check-0.18.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 Nov 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.
