Check Info Tool — ATE Program Test Condition Extractor
Quickly extract test conditions from Teradyne IG-XL test programs
Table of Contents
Overview
The Check Info Tool streamlines the process of extracting critical test conditions from Teradyne IG-XL ATE test programs. This tool helps engineers quickly and accurately retrieve information such as pattern usage, flow binning details, power pin levels, and AC/timing data — significantly reducing the time and effort required for program quality checks.
Background
- Challenge: Engineers often need to manually search through ATE test programs to find specific test conditions, a process that is both time-consuming and prone to errors.
- Solution: Check Info Tool automates the extraction and presents results in a structured Excel report (.xlsm), with both a GUI and a CLI for flexible integration.
Features
- Automated Extraction of Test Conditions — flow table, DC/AC spec, timing, and pattern set per job
- Pattern Usage Identification — maps patterns to test instances with period and clock information
- Flow Binning Information Retrieval — sort bin descriptions across all test suites
- Power Pin Level Extraction — per-instance DPS voltage levels with power order support
- AC/Timing Data Extraction — timing period and MCG clock values (Period or Frequency mode)
- VBT Naming Convention Checker — optional static analysis of VBT
.basfiles - CLI Interface — scriptable, JSON output, AI agent friendly
- GUI Interface — point-and-click workflow for interactive use
Installation
Requirements
- Python 3.9 – 3.14
- Windows, macOS (Apple Silicon), or Linux
Install from PyPI (Recommended)
pip install check-info-tool
After installation, the check-info command is immediately available:
check-info --version
check-info --help
Usage
CLI Usage
# List all jobs in a test program
check-info list -d <program.igxl> -p <platform>
# Run analysis on all jobs
check-info run -d <program.igxl> -p <platform> -j all -o ./results
# Run specific job
check-info run -d <program.igxl> -p <platform> -j "Job_FT" -o ./results
# Machine-readable JSON output (useful for scripting)
check-info list -d <program.igxl> -p UltraFLEXplus --json
See docs/cli-usage.md for the full CLI reference including all flags, examples, and agent integration patterns.
GUI Usage
Launch the graphical interface:
check-info gui
Workflow
- Load a test program — use File → Import Program File to select a
.igxl/.zip/.xlsmfile, or Import Program Directory for an extracted ASCII directory - Select platform — choose
UltraFLEXplus,UltraFLEX, orJ750 - Configure options — set cycle mode (Period/Frequency), spec environment, power order file, pattern path
- Click Load — the job list will appear; select the jobs you want to analyse
- Click Run — the
.xlsmreport is generated in the project directory
Supported Platforms
| Tester | Input Formats |
|---|---|
| UltraFLEXplus | .igxl, .zip, .xlsm, directory |
| UltraFLEX | .igxl, .zip, .xlsm, directory |
| J750 | .igxl, .zip, .xlsm, directory |
License
This software is proprietary. See LICENSE for full terms.
For licensing enquiries: zhouchao486@gmail.com
Built for the semiconductor ATE community
1 maintainer
Metadata
1 maintainer
Release files for check-info-tool 1.8.8
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distributions (wheels)
Total release size: 38.3 MB
Release files / check_info_tool-1.8.8-cp314-cp314-win_amd64.whl
| Download URL | check_info_tool-1.8.8-cp314-cp314-win_amd64.whl |
|---|---|
| Size | 643.5 kB |
| Tags | CPython 3.14 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
ee8f1bdeea1349caac7d903086d7948f96bf7de35ec35819ba4d8ecbb0699aa3
|
|
BLAKE2b-256 checksum How to use checksums |
da110cfb87aa1b800b4a33b1210860186c3f76237652168d635297e029418d2e
|
| 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 Apr 28, 2026.
Transparency logRelease files / check_info_tool-1.8.8-cp314-cp314-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
| Download URL | check_info_tool-1.8.8-cp314-cp314-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl |
|---|---|
| Size | 5.0 MB |
| Tags | CPython 3.14 Linux glibc 2.17+ x86-64 Linux glibc 2.28+ x86-64 |
|
SHA-256 checksum How to use checksums |
9a27d9ebc222ae043e25cb134593f750591ec8b8f36b09aa90c3de66f62b4fb7
|
|
BLAKE2b-256 checksum How to use checksums |
6f103d1a2e200a62d334b3da67336ed138a701f68b22dddb6bc607db0cab3e48
|
| 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 Apr 28, 2026.
Transparency logRelease files / check_info_tool-1.8.8-cp314-cp314-macosx_11_0_arm64.whl
| Download URL | check_info_tool-1.8.8-cp314-cp314-macosx_11_0_arm64.whl |
|---|---|
| Size | 708.7 kB |
| Tags | CPython 3.14 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
b70748a17da1c83fe8274db715e3ad08dc84d33e63690f120a6298cc73fdf09a
|
|
BLAKE2b-256 checksum How to use checksums |
8a9d1d3a2e93539e8848d1673b45efa76381622835d97989e4752e9a25d92f4f
|
| 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 Apr 28, 2026.
Transparency logRelease files / check_info_tool-1.8.8-cp313-cp313-win_amd64.whl
| Download URL | check_info_tool-1.8.8-cp313-cp313-win_amd64.whl |
|---|---|
| Size | 631.6 kB |
| Tags | CPython 3.13 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
6a5455e84ff061eb9fa4fcd270252431dd43a56b5fd277c18afb5e4a7a6fc93f
|
|
BLAKE2b-256 checksum How to use checksums |
5cb1aed723d5df37a91df7c8abd4a40090df96f6dac05c66d4a3942dddbb3107
|
| 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 Apr 28, 2026.
Transparency logRelease files / check_info_tool-1.8.8-cp313-cp313-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
| Download URL | check_info_tool-1.8.8-cp313-cp313-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl |
|---|---|
| Size | 5.0 MB |
| Tags | CPython 3.13 Linux glibc 2.17+ x86-64 Linux glibc 2.28+ x86-64 |
|
SHA-256 checksum How to use checksums |
c01d36e5838a9e9489a2fd89bb31dc623ec1b56cb0be63c3cd08584630ba4978
|
|
BLAKE2b-256 checksum How to use checksums |
362ef11186b1825bfb0dfecc0cae7ed1c159b6fba671f24d8fc0138f878c09ec
|
| 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 Apr 28, 2026.
Transparency logRelease files / check_info_tool-1.8.8-cp313-cp313-macosx_11_0_arm64.whl
| Download URL | check_info_tool-1.8.8-cp313-cp313-macosx_11_0_arm64.whl |
|---|---|
| Size | 705.3 kB |
| Tags | CPython 3.13 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
72e0989fa53d8ae374846c9818609b24c8446c03f22eaeeef830b94595d0caa0
|
|
BLAKE2b-256 checksum How to use checksums |
d540ec53a02bc9d215b7b1036b04274163fd629eb63d624778b3c7891339f3a7
|
| 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 Apr 28, 2026.
Transparency logRelease files / check_info_tool-1.8.8-cp312-cp312-win_amd64.whl
| Download URL | check_info_tool-1.8.8-cp312-cp312-win_amd64.whl |
|---|---|
| Size | 635.8 kB |
| Tags | CPython 3.12 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
35f0df3a347c42fa2db4cb6f277caaadb1a5fd068a93751f89fa8dd1e63370e0
|
|
BLAKE2b-256 checksum How to use checksums |
12449003fb698383b97dee80797e8464804a153d416c98a99d3de226225362ee
|
| 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 Apr 28, 2026.
Transparency logRelease files / check_info_tool-1.8.8-cp312-cp312-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
| Download URL | check_info_tool-1.8.8-cp312-cp312-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl |
|---|---|
| Size | 5.1 MB |
| Tags | CPython 3.12 Linux glibc 2.17+ x86-64 Linux glibc 2.28+ x86-64 |
|
SHA-256 checksum How to use checksums |
ef4d548cc7f905c90c0c2a88f9947f623dcdc6af9242ade380a52aa4571fe1dd
|
|
BLAKE2b-256 checksum How to use checksums |
3b338127007ce201daf5e2c249fec430d03b7f1fd41b6639fa75f09c7e46f319
|
| 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 Apr 28, 2026.
Transparency logRelease files / check_info_tool-1.8.8-cp312-cp312-macosx_11_0_arm64.whl
| Download URL | check_info_tool-1.8.8-cp312-cp312-macosx_11_0_arm64.whl |
|---|---|
| Size | 712.0 kB |
| Tags | CPython 3.12 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
d245f003fbc66157d9eb98224bb0d6993cd877dc9d81972c54cc1cc21213a99f
|
|
BLAKE2b-256 checksum How to use checksums |
02d8de34f27e63046ceae19d15954cc0c9826ee58ca4f872051904db59866660
|
| 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 Apr 28, 2026.
Transparency logRelease files / check_info_tool-1.8.8-cp311-cp311-win_amd64.whl
| Download URL | check_info_tool-1.8.8-cp311-cp311-win_amd64.whl |
|---|---|
| Size | 646.5 kB |
| Tags | CPython 3.11 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
33c345c8f412c7d5c90fd29fdadc81ec0a2316628ce92ae0bc6148b9db8aa43a
|
|
BLAKE2b-256 checksum How to use checksums |
57adf6fa04211c41fe80677918d74f3326222c3da716dcbf93e4d481ea59013b
|
| 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 Apr 28, 2026.
Transparency logRelease files / check_info_tool-1.8.8-cp311-cp311-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
| Download URL | check_info_tool-1.8.8-cp311-cp311-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl |
|---|---|
| Size | 5.2 MB |
| Tags | CPython 3.11 Linux glibc 2.17+ x86-64 Linux glibc 2.28+ x86-64 |
|
SHA-256 checksum How to use checksums |
bd64280cfed852adb903512f10dc957bd99c57c06f2854df80479f47d193defe
|
|
BLAKE2b-256 checksum How to use checksums |
8c370bf628de9474a62ba6bd1d0a5a6b40de21ed835d0e50fe06fd446458b24f
|
| 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 Apr 28, 2026.
Transparency logRelease files / check_info_tool-1.8.8-cp311-cp311-macosx_11_0_arm64.whl
| Download URL | check_info_tool-1.8.8-cp311-cp311-macosx_11_0_arm64.whl |
|---|---|
| Size | 712.5 kB |
| Tags | CPython 3.11 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
b1d4c251d76b8bdd3df1b38dd1b673127fb52c17cbcef3e8a14f5f92db29589c
|
|
BLAKE2b-256 checksum How to use checksums |
5abc0654e303ad0fbd773d0eaca3bc58fd87da2474c831793571d181482d1862
|
| 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 Apr 28, 2026.
Transparency logRelease files / check_info_tool-1.8.8-cp310-cp310-win_amd64.whl
| Download URL | check_info_tool-1.8.8-cp310-cp310-win_amd64.whl |
|---|---|
| Size | 644.5 kB |
| Tags | CPython 3.10 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
b347b7e170892c98373b3d90d30b5d1095c0dfd8a5a352ac1a494260fed86d73
|
|
BLAKE2b-256 checksum How to use checksums |
5bcdd369ebd14d52a5a1480f6b062442857f1458a3ccf2e9a506223b8d668a2e
|
| 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 Apr 28, 2026.
Transparency logRelease files / check_info_tool-1.8.8-cp310-cp310-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
| Download URL | check_info_tool-1.8.8-cp310-cp310-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl |
|---|---|
| Size | 4.9 MB |
| Tags | CPython 3.10 Linux glibc 2.17+ x86-64 Linux glibc 2.28+ x86-64 |
|
SHA-256 checksum How to use checksums |
df60a5f5a21ceb6ec68872a6c9484433e495d0180acb2117c0454e560b065413
|
|
BLAKE2b-256 checksum How to use checksums |
5739c9b8758309ae7890dc6fbb422de7259239fa205412ea31e519d141a4785b
|
| 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 Apr 28, 2026.
Transparency logRelease files / check_info_tool-1.8.8-cp310-cp310-macosx_11_0_arm64.whl
| Download URL | check_info_tool-1.8.8-cp310-cp310-macosx_11_0_arm64.whl |
|---|---|
| Size | 715.7 kB |
| Tags | CPython 3.10 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
2ae69a65882a27e2e187066018eea0b003d8f025490aebc7f66a2d5b2ac4a925
|
|
BLAKE2b-256 checksum How to use checksums |
384fc012e8215e8c5b08c1bbff8d02920c528163b3af53016a76bca922cc70bb
|
| 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 Apr 28, 2026.
Transparency logRelease files / check_info_tool-1.8.8-cp39-cp39-win_amd64.whl
| Download URL | check_info_tool-1.8.8-cp39-cp39-win_amd64.whl |
|---|---|
| Size | 647.0 kB |
| Tags | CPython 3.9 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
73e76c1060ba259364f0e092ae4bcdd8394081874a51c96d66726818340b4f71
|
|
BLAKE2b-256 checksum How to use checksums |
8b4b4f2bab553dd676ce7b0ba9fe9df68a7f675842dacb863dca3bdf67526b54
|
| 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 Apr 28, 2026.
Transparency logRelease files / check_info_tool-1.8.8-cp39-cp39-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
| Download URL | check_info_tool-1.8.8-cp39-cp39-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl |
|---|---|
| Size | 4.9 MB |
| Tags | CPython 3.9 Linux glibc 2.17+ x86-64 Linux glibc 2.28+ x86-64 |
|
SHA-256 checksum How to use checksums |
aeab49b64a6fd9fb74941289b0aea8f66aae56f154f86969122bdee36a5a1501
|
|
BLAKE2b-256 checksum How to use checksums |
4b91e7837000cfc4cf9db9b8777682112b2348baa81a1f10239ddc4b5dee7be5
|
| 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 Apr 28, 2026.
Transparency logRelease files / check_info_tool-1.8.8-cp39-cp39-macosx_11_0_arm64.whl
| Download URL | check_info_tool-1.8.8-cp39-cp39-macosx_11_0_arm64.whl |
|---|---|
| Size | 719.5 kB |
| Tags | CPython 3.9 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
15397e119471a840486abb245aabe03e71865eeeec0e9a9f26c803003e24f351
|
|
BLAKE2b-256 checksum How to use checksums |
9df11ecfd773d7939d1e2f97eb3836dc1454c441c733951ea7c3b3bd012fc4f8
|
| 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 Apr 28, 2026.
Transparency logSecurity for check-info-tool 1.8.8
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 18 files in this release have been uploaded with provenance metadata.
Attestation for check_info_tool-1.8.8-cp314-cp314-win_amd64.whl
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 Apr 28, 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.
