The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for pyrdf4j 0.1.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 | |
|---|---|---|---|---|
| pyrdf4j-0.1.1.tar.gz | 10.0 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| pyrdf4j-0.1.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 35.6 kB
Release files / pyrdf4j-0.1.1.tar.gz
| Download URL | pyrdf4j-0.1.1.tar.gz |
|---|---|
| Size | 10.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
79a1895755c2dd4b7bf2fd80b56e44ea0b6b7dada3bc73d37a4768845a709995
|
|
BLAKE2b-256 checksum How to use checksums |
d1671a8b90ea47c3dd9189d45a365396dd46751321ef5a56218de8420916a4a2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.8.3 CPython/3.11.2 Linux/6.1.0-25-amd64
|
Release files / pyrdf4j-0.1.1-py3-none-any.whl
| Download URL | pyrdf4j-0.1.1-py3-none-any.whl |
|---|---|
| Size | 25.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
edd25f234efd59b68cc15dec9c56734462217cd740d352f38fae2c349610d16c
|
|
BLAKE2b-256 checksum How to use checksums |
6711b814577893e12e588c8cc609c9dbdbff96c010e15ddfd6ce2e0002f80e14
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.8.3 CPython/3.11.2 Linux/6.1.0-25-amd64
|
Security for pyrdf4j 0.1.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.
