This release is a pre-release and may not be stable for production use.
Nin0 war hier
Ogu aber auch
This gon' be epic now
1 maintainer
Metadata
1 maintainer
Release files for pysar-core 0.1.0a2
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 |
|---|---|---|---|---|
| pysar_core-0.1.0a2.tar.gz | 1.6 MB | With provenance | Details for pysar_core-0.1.0a2.tar.gz |
Built distributions (wheels)
Total release size: 19.3 MB
Release files / pysar_core-0.1.0a2.tar.gz
| Download URL | pysar_core-0.1.0a2.tar.gz |
|---|---|
| Size | 1.6 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
2c054c6a814f7a18cebf381eb912b46d8936b0fdf1614a1b1c7b11a56a734e5c
|
|
BLAKE2b-256 checksum How to use checksums |
4b83b9062f14ef2e61080b1d81686184307bfe5bd3257070e0285efb9422e72c
|
| 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 6, 2026.
Transparency logRelease files / pysar_core-0.1.0a2-cp311-abi3-win_arm64.whl
| Download URL | pysar_core-0.1.0a2-cp311-abi3-win_arm64.whl |
|---|---|
| Size | 1.5 MB |
| Tags | CPython 3.11 Windows ARM64 abi3 |
|
SHA-256 checksum How to use checksums |
4478e4a669f9d363c636360d45bf43bba3b6d94f90213fc92a1e8d26b4d6eded
|
|
BLAKE2b-256 checksum How to use checksums |
7ba5314108a800567f01c40589d83d70187be056963d1354c5957d9188efedb9
|
| 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 6, 2026.
Transparency logRelease files / pysar_core-0.1.0a2-cp311-abi3-win_amd64.whl
| Download URL | pysar_core-0.1.0a2-cp311-abi3-win_amd64.whl |
|---|---|
| Size | 1.5 MB |
| Tags | CPython 3.11 Windows x86-64 abi3 |
|
SHA-256 checksum How to use checksums |
7b98dc821215e7f01b389dd10cad030faa25a71c0d89d0d0cb72bd47456297a7
|
|
BLAKE2b-256 checksum How to use checksums |
3096212bedf7c413ce6c6e3221961b2b05d0b4c2d37322c15651ffba5dc88833
|
| 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 6, 2026.
Transparency logRelease files / pysar_core-0.1.0a2-cp311-abi3-musllinux_1_2_x86_64.whl
| Download URL | pysar_core-0.1.0a2-cp311-abi3-musllinux_1_2_x86_64.whl |
|---|---|
| Size | 2.9 MB |
| Tags | CPython 3.11 Linux musl 1.2+ x86-64 abi3 |
|
SHA-256 checksum How to use checksums |
15c5f4bd9ee448a1409602e9fa577a303e83f99b71b127ae94a635009f44e934
|
|
BLAKE2b-256 checksum How to use checksums |
33261e948661b96197e26d06a87427ab5fd6c246f4bdd80d972d9bb7a84892ac
|
| 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 6, 2026.
Transparency logRelease files / pysar_core-0.1.0a2-cp311-abi3-musllinux_1_2_aarch64.whl
| Download URL | pysar_core-0.1.0a2-cp311-abi3-musllinux_1_2_aarch64.whl |
|---|---|
| Size | 2.8 MB |
| Tags | CPython 3.11 Linux musl 1.2+ ARM64 abi3 |
|
SHA-256 checksum How to use checksums |
8c1278cc3afe991a18ad01f0e46bc6f036f29aef17941cbd87e8e0e82bf43c25
|
|
BLAKE2b-256 checksum How to use checksums |
468d164037ed0913c21d3c7803ed5c2b7b8e2cd4d8830052d0a4e764819ffe3f
|
| 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 6, 2026.
Transparency logRelease files / pysar_core-0.1.0a2-cp311-abi3-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
| Download URL | pysar_core-0.1.0a2-cp311-abi3-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl |
|---|---|
| Size | 2.9 MB |
| Tags | CPython 3.11 Linux glibc 2.17+ x86-64 Linux glibc 2.28+ x86-64 abi3 |
|
SHA-256 checksum How to use checksums |
841321f0de01b510be281e16db485726a876c2d880bdc1c63fb5de722cb378ae
|
|
BLAKE2b-256 checksum How to use checksums |
092e166bb2c05d2b94505391d810dd2c08b0eebb46d825f6389117b1ef50443f
|
| 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 6, 2026.
Transparency logRelease files / pysar_core-0.1.0a2-cp311-abi3-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl
| Download URL | pysar_core-0.1.0a2-cp311-abi3-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl |
|---|---|
| Size | 2.8 MB |
| Tags | CPython 3.11 Linux glibc 2.17+ ARM64 Linux glibc 2.28+ ARM64 abi3 |
|
SHA-256 checksum How to use checksums |
af7116a5d6492d46176ebde4fa15da8124048e879c07b471af67d359d170045e
|
|
BLAKE2b-256 checksum How to use checksums |
014a31ac8f26a773a17bc207742f6ddc38430fbf91bb98a76f636bee844c18fd
|
| 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 6, 2026.
Transparency logRelease files / pysar_core-0.1.0a2-cp311-abi3-macosx_11_0_x86_64.whl
| Download URL | pysar_core-0.1.0a2-cp311-abi3-macosx_11_0_x86_64.whl |
|---|---|
| Size | 1.6 MB |
| Tags | CPython 3.11 abi3 macOS 11.0+ x86-64 |
|
SHA-256 checksum How to use checksums |
4632767ae4d99dece9ce18c7696797e5665935bcb58a6f59777dceb76036372d
|
|
BLAKE2b-256 checksum How to use checksums |
d8d231ab49c60a6c7a9e8d2dbee73600d520ef1414fc5270de081bb46b1183d1
|
| 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 6, 2026.
Transparency logRelease files / pysar_core-0.1.0a2-cp311-abi3-macosx_11_0_arm64.whl
| Download URL | pysar_core-0.1.0a2-cp311-abi3-macosx_11_0_arm64.whl |
|---|---|
| Size | 1.6 MB |
| Tags | CPython 3.11 abi3 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
504e3697ecf7c0b14a3ca8176f5fd627bb93998a847b911a4415abb4f393d424
|
|
BLAKE2b-256 checksum How to use checksums |
8e6ef4550f454cb290166fff8b25b58ac94758751a8cf947bae80c5f22dfcf4a
|
| 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 6, 2026.
Transparency logSecurity for pysar-core 0.1.0a2
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 9 files in this release have been uploaded with provenance metadata.
Attestation for pysar_core-0.1.0a2.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 6, 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.
