CalDAV2ICS
A script that downloads all calendars from a CalDAV server and caches them locally as static
.ics files.
Passwords are never written to disk: the local cache stores only synced calendar data, and credentials are stripped before saving.
Prerequisites
- Python 3.10 to 3.14.
Installation
pip install caldav2ics
Usage
Create a config .toml file with one section per CalDAV server:
[server_a]
url = "https://caldav.server_a.com/calendar/remote.php/dav/calendars/user/"
user = "user"
save-dir = "/absolute/path/to/calendars/server_a"
[server_b]
...
save-dir must be an absolute path. Run the sync:
caldav2ics config.toml
This prompts for the password. To provide it non-interactively, set C2I_PASSWORD instead:
C2I_PASSWORD=$(cat .password) caldav2ics config.toml
Each server writes a cache.pkl (its synced state, used for incremental updates) and one .ics
file per calendar into its save-dir:
calendars/server_a/
calendar1.ics
calendar2.ics
cache.pkl
To integrate with Google Calendar, either upload the .ics files or host save-dir publicly
(add basic auth or similar for access control; for stronger security, use a different method).
License
This project is licensed under the MIT license. See LICENSE for details.
1 maintainer
Metadata
1 maintainer
Release files for caldav2ics 0.1.2
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 | Actions |
|---|---|---|---|---|
| caldav2ics-0.1.2.tar.gz | 10.9 kB | With provenance | Details for caldav2ics-0.1.2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| caldav2ics-0.1.2-py3-none-any.whl | Python 3 | none | any | Details for caldav2ics-0.1.2-py3-none-any.whl |
Total release size: 17.6 kB
Release files / caldav2ics-0.1.2.tar.gz
| Download URL | caldav2ics-0.1.2.tar.gz |
|---|---|
| Size | 10.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
116a5f69e9535d9e4f9b48fbae424a55929002a15848589fbf96ba097879ba30
|
|
BLAKE2b-256 checksum How to use checksums |
62e8c75bda7f91b4eefe6df0314a29b33ced2ca23f8db612115a06ed23b70962
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 27, 2026.
Transparency logRelease files / caldav2ics-0.1.2-py3-none-any.whl
| Download URL | caldav2ics-0.1.2-py3-none-any.whl |
|---|---|
| Size | 6.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
fcf5f8a4eb190f430119a7093c6f1f88046216bb8b527950431bcd6fce568177
|
|
BLAKE2b-256 checksum How to use checksums |
21ce422211aea7b4ebbb6b607e8e66414ef33601021fa74c5014cd4f15201891
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 27, 2026.
Transparency logSecurity for caldav2ics 0.1.2
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.
Full provenance
Both files in this release have been uploaded with provenance metadata.
Attestation for caldav2ics-0.1.2.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 27, 2026.
Transparency logA 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.
