The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for autoscorecard 0.1.0
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 | |
|---|---|---|---|---|
| autoscorecard-0.1.0.tar.gz | 1.7 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| autoscorecard-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 3.4 kB
Release files / autoscorecard-0.1.0.tar.gz
| Download URL | autoscorecard-0.1.0.tar.gz |
|---|---|
| Size | 1.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
617ade27edd3d90b2a43379e92b24c5d60ad3fb978d1e7ce452e655dbab9d522
|
|
BLAKE2b-256 checksum How to use checksums |
15a4f2b50bdd4ddfb23faa806cbd0db77b4e66007e7d5b236313b121b7ac0ff9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.9.12
|
Release files / autoscorecard-0.1.0-py3-none-any.whl
| Download URL | autoscorecard-0.1.0-py3-none-any.whl |
|---|---|
| Size | 1.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
4607fe21a6ab4991b24daa41ecd73ebe94b91e077eb8161c3327b6ba715a4a62
|
|
BLAKE2b-256 checksum How to use checksums |
e8d91c7a8833aea115980f1f45458e5dec8b68f58dc8699a893a461d6fb190c2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.9.12
|
Security for autoscorecard 0.1.0
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.
