Example Package
This is a simple example package. You can use GitHub-flavored Markdown to write your content.
Metadata
Release files for nanophotonics 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 | |
|---|---|---|---|---|
| nanophotonics-0.0.1.tar.gz | 1.5 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| nanophotonics-0.0.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 3.9 kB
Release files / nanophotonics-0.0.1.tar.gz
| Download URL | nanophotonics-0.0.1.tar.gz |
|---|---|
| Size | 1.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
183bf50561fe772ab8b56485e6608651130079cef4173506a5c486d9d6d2808f
|
|
BLAKE2b-256 checksum How to use checksums |
bbb59ded3273b433729585f35c513f2c150ad2108d8d904c3f914a5a21f5b6da
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.1 CPython/3.12.2
|
Release files / nanophotonics-0.0.1-py3-none-any.whl
| Download URL | nanophotonics-0.0.1-py3-none-any.whl |
|---|---|
| Size | 2.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
2cd7f910e2e34992431c81169de200f5ae89c1f4b4e7d50f22831babc664a830
|
|
BLAKE2b-256 checksum How to use checksums |
ab32b38d4790eaa775becf7a42fa7f6f7b37ca9db266196f1e4ba0e0297d9e79
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.1 CPython/3.12.2
|
Security for nanophotonics 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.