The author of this package has not provided a project description
2 maintainers
Metadata
2 maintainers
Release files for TracDashesSyntaxPlugin 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 | |
|---|---|---|---|---|
| TracDashesSyntaxPlugin-1.1.tar.gz | 1.7 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| TracDashesSyntaxPlugin-1.1-py2-none-any.whl | Python 2 | none | any | Details |
Total release size: 4.4 kB
Release files / TracDashesSyntaxPlugin-1.1.tar.gz
| Download URL | TracDashesSyntaxPlugin-1.1.tar.gz |
|---|---|
| Size | 1.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f7d56cbe1ba91d8dc6f53d2e20545a80fc0ec9266bb80bd44f2d38ac81112076
|
|
BLAKE2b-256 checksum How to use checksums |
de546ea58338b3fc4ba73510a12fce14f3aaf1648fc62c50eda4ec20d258a105
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Release files / TracDashesSyntaxPlugin-1.1-py2-none-any.whl
| Download URL | TracDashesSyntaxPlugin-1.1-py2-none-any.whl |
|---|---|
| Size | 2.6 kB |
| Tags | Python 2 |
|
SHA-256 checksum How to use checksums |
fd12bdc991b78ca7aa9c767f5ff16e704674e0b77705fe8e0a23d954dedcda4f
|
|
BLAKE2b-256 checksum How to use checksums |
7c6935cdb7c4e36d39cf9a92373fa6852f04225d8ee2a36de26b968c8b968509
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for TracDashesSyntaxPlugin 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.
