The author of this package has not provided a project description
Metadata
Release files for auto-import-syspath 0.1.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 | |
|---|---|---|---|---|
| auto_import_syspath-0.1.2.tar.gz | 1.8 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| auto_import_syspath-0.1.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 4.2 kB
Release files / auto_import_syspath-0.1.2.tar.gz
| Download URL | auto_import_syspath-0.1.2.tar.gz |
|---|---|
| Size | 1.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
7789d0ba9838ed8bf3be8f1e51770a555e99a7da0993b21abede2bb720fdbd42
|
|
BLAKE2b-256 checksum How to use checksums |
6e03e69111a29042940a00a00f2b5edb7c9adb1a175c607b56f4ec3144ed7ebe
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.0.0 CPython/3.11.7
|
Release files / auto_import_syspath-0.1.2-py3-none-any.whl
| Download URL | auto_import_syspath-0.1.2-py3-none-any.whl |
|---|---|
| Size | 2.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
96515cd6d205e24962288b12be99e3bb8f3fde42b1d92d395e3a670f3f45c6f6
|
|
BLAKE2b-256 checksum How to use checksums |
30742d6ffd966967c234537797e9395d3f9351a4dcff5cec56cbbe16254f8dba
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.0.0 CPython/3.11.7
|
Security for auto-import-syspath 0.1.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.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A 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.