This release is a pre-release and may not be stable for production use.
========TK_DRAFT=========
Cronk: a cron-json translator
This repository is a part of the Google Open Source Blog's "From zero to supply-chain security hero" blog series. It is meant for demonstrative purposes, and should not be used in production!
All information beyond this point is fictional!
- Student: Alice Doe (@nebraska-dev), 2018Q4
- Course: TK_FUNNY_COURSE_NAME_42 @ Cottonwood University (TK Cottonwood is the Nebraska state tree, and there is no such university)
Cronk allows developers to convert files between the crontab and json formats.
To-do:
- Add i18n of periodicity via Babel
Release to pypi.org
We provide a Dockerfile that sets up the correct environment to publish a new version of Cronk to PyPI.
*These instructions assume the build is executed on a Cloudtop instance.
First time Docker setup
Remove any previous Docker installation:
sudo apt remove docker-engine
Add Google's Docker distribution repository to `apt:
glinux-add-repo docker-ce-"$(lsb_release -cs)"
Install the Docker runtime:
sudo apt update && sudo apt install docker-ce
Check that the Docker daemon is active:
systemctl status docker.service
The systemctl output should look something like this:
ltadeut@ltadeut-devbox:~/cronk$ systemctl status docker.service
● docker.service - Docker Application Container Engine
Loaded: loaded (/usr/lib/systemd/system/docker.service; enabled; preset: enabled)
Active: active (running) since Tue 2025-09-16 16:29:58 UTC; 1h 54min ago
Invocation: f59978f5efe2458d904819d125f79a03
TriggeredBy: ● docker.socket
Docs: https://docs.docker.com
Main PID: 2421936 (dockerd)
Tasks: 32
Memory: 1.2G (peak: 1.2G)
CPU: 2min 21.072s
CGroup: /system.slice/docker.service
└─2421936 /usr/bin/dockerd -H fd:// --containerd=/run/containerd/containerd.sock
Update the cronk version
To release a new version, you must first update the version listed in the pyproject.toml file.
Open the pyproject.toml file at the root of this repository and edit the version field.
Generate the base image
Run the command below from the repository's root directory:
sudo docker build -t release-cronk-to-pypi -f docker/Dockerfile.release_pypi .
Publish to pypi.org
Run the command below to execute the release image (replace <PYPI_API_TOKEN> with the value found in https://valentine.corp.google.com/#/show/1757341155550459?tab=metadata):
sudo docker run -e TWINE_PASSWORD=<PYPI_API_TOKEN> release-cronk-to-pypi
1 maintainer
Metadata
1 maintainer
Release files for cronk 0.0.19rc16
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 | |
|---|---|---|---|---|
| cronk-0.0.19rc16.tar.gz | 9.1 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| cronk-0.0.19rc16-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 18.7 kB
Release files / cronk-0.0.19rc16.tar.gz
| Download URL | cronk-0.0.19rc16.tar.gz |
|---|---|
| Size | 9.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
0467ea7bd781a2cf23bc60dbc9465bc314537f113a19cd64f17d9b95445418fe
|
|
BLAKE2b-256 checksum How to use checksums |
ae52a92459af439907c2b336b9e16f5ab3d6b97efef89eafda44867a5c924019
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.6
|
Release files / cronk-0.0.19rc16-py3-none-any.whl
| Download URL | cronk-0.0.19rc16-py3-none-any.whl |
|---|---|
| Size | 9.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
86de32a7861faa695f3856ba0b94cb164a7f187125687cecca7ea83cea40a957
|
|
BLAKE2b-256 checksum How to use checksums |
cde3f65936fd5abeb05356ce5b7ebcc82468dc03ed1b61c754a5956617dad886
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.6
|
Security for cronk 0.0.19rc16
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.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
