The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for app-injector 0.0.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 | |
|---|---|---|---|---|
| app_injector-0.0.2.tar.gz | 989 Bytes | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| app_injector-0.0.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 2.7 kB
Release files / app_injector-0.0.2.tar.gz
| Download URL | app_injector-0.0.2.tar.gz |
|---|---|
| Size | 989 Bytes |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
6598721b9316ec1d31a97ae19aafda956d76dcac4629ef8a69045bd2eff1c482
|
|
BLAKE2b-256 checksum How to use checksums |
fb411bc40d3ade7f23e9d2380b6c04aa2081d2db7dc6fc59cbd279f9d47e327c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.1 CPython/3.12.3
|
Release files / app_injector-0.0.2-py3-none-any.whl
| Download URL | app_injector-0.0.2-py3-none-any.whl |
|---|---|
| Size | 1.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
3d07ffd8399d0034d53a7a8ba771861ba39606fe8e53b67d9c57584674005586
|
|
BLAKE2b-256 checksum How to use checksums |
0660899549065eaeba251336b6beba3ca954a30ac22c68afcafe619942808bad
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.1 CPython/3.12.3
|
Security for app-injector 0.0.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.
