This release is a pre-release and may not be stable for production use.
UNKNOWN
Metadata
Release files for archipel-agent-action-scheduler 0.6.0beta
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distributions (wheels)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| archipel_agent_action_scheduler-0.6.0beta-py2.7.egg | Legacy Egg format | - | - | Details |
| archipel_agent_action_scheduler-0.6.0beta-py2.6.egg | Legacy Egg format | - | - | Details |
Total release size: 25.9 kB
Release files / archipel_agent_action_scheduler-0.6.0beta-py2.7.egg
| Download URL | archipel_agent_action_scheduler-0.6.0beta-py2.7.egg |
|---|---|
| Size | 12.9 kB |
| Tags | Egg |
|
SHA-256 checksum How to use checksums |
29096a28cb291a9a517a883b219f674751fc751067fe1d1720ba0ebef7102626
|
|
BLAKE2b-256 checksum How to use checksums |
f8968e9ea0eac52c2716ec08d3a10f66e3e982ecd977e2fc758914a05e83da09
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Release files / archipel_agent_action_scheduler-0.6.0beta-py2.6.egg
| Download URL | archipel_agent_action_scheduler-0.6.0beta-py2.6.egg |
|---|---|
| Size | 12.9 kB |
| Tags | Egg |
|
SHA-256 checksum How to use checksums |
4e34bd683fa27c0604a723dcba96aa8387871c7b96d0e69eaf28c05bab0f7418
|
|
BLAKE2b-256 checksum How to use checksums |
efbdbd1f45582a1fd72eb8fb5c49ba90f848c40eeb5dbe4de8baa2ed2d4b111e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for archipel-agent-action-scheduler 0.6.0beta
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.