The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for pythonvba 0.0.1
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 | |
|---|---|---|---|---|
| pythonvba-0.0.1.tar.gz | 1.4 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| pythonvba-0.0.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 3.1 kB
Release files / pythonvba-0.0.1.tar.gz
| Download URL | pythonvba-0.0.1.tar.gz |
|---|---|
| Size | 1.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
00eb6d91e77cd5a8cd3a0a698959324c1f509c4070b1dd4ba9f6e3cba4036da6
|
|
BLAKE2b-256 checksum How to use checksums |
3f1a5936802f10b86356bf2f88fe56bd095cc47f7b79d8a8e4d897eeeeb34908
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.10.11
|
Release files / pythonvba-0.0.1-py3-none-any.whl
| Download URL | pythonvba-0.0.1-py3-none-any.whl |
|---|---|
| Size | 1.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
d6a4cb6308f130b37437ddfc4ba9e8feb430bd66c20c172dec16ee8a8124e1e6
|
|
BLAKE2b-256 checksum How to use checksums |
379b45bc699f2255f1852b366e4514894f03ead1d5b5e36ae78da0db1e69ec3d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.10.11
|
Security for pythonvba 0.0.1
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.
