gog is a comprehensive, production-grade CLI tool for Google Workspace automation that unifies 20+ Google services (Gmail, Calendar, Drive, Docs, Sheets, Slides, Forms, Meet, Chat, Contacts, Tasks, Classroom, YouTube, Analytics, Search Console, Admin, Groups, Keep, Photos, Maps, Apps Script) into a single binary. It excels at task-first workflows: searching and sanitizing mail, resolving calendar names, auditing Drive sharing, editing Docs, appending Sheet tables, building Slides from Markdown, managing Workspace users, and performing encrypted backups. The architecture is a modular monolith with clean internal package boundaries for each service domain. Key entry points are cmd/gog/main.go and the Kong-based command tree in internal/cmd. Primary data flows: command invocation -> account/client resolution -> authenticated Google API client creation -> API execution -> structured output (JSON, plain TSV, or human-readable tables). External dependencies include Google APIs, OAuth2, keyring backends (macOS Keychain, Windows Credential Manager, Linux Secret Service, encrypted file), MCP for agent integration, and age encryption for backups. The codebase demonstrates exceptional craftsmanship in cross-platform secret storage, Gmail push notification processing, sed-style Docs editing with UTF-16 index tracking, atomic Docs request batching, encrypted backup with Git shard checkpointing, email open tracking with versioned key rotation and bot detection, and build-time safety profile compilation to hash-based allow/deny switches. Active development with recent commits, comprehensive test coverage (unit + integration + live tests), and modern dependency versions.
This is the `holidays` Python library, a fast, efficient tool for generating country-, province-, state-, and financial-market-specific holiday calendars on the fly. It supports over 250 ISO 3166-1 countries (with subdivisions) and 25+ financial exchanges (NYSE, NASDAQ, LSE, etc.), using a mixin-based composition pattern to combine calendar systems (Gregorian, Islamic, Hebrew, Chinese, Hindu, Buddhist, etc.) with localization in dozens of languages. The library is designed for integration into applications that need to check whether a date is a holiday, retrieve holiday names, or export calendars to iCal format. It is not a data research project; it is a well-engineered Python library with a clean public API (`holidays.US()`, `holidays.country_holidays('US')`), extensive test coverage (100% code coverage enforced), and a robust observed-holiday rule system. The codebase demonstrates high craftsmanship through its reusable mixin pattern, configurable observed rules, and a generic iCal exporter. It is actively maintained with frequent commits, CI/CD pipelines, and dependabot integration.
This repository is a highly configurable, feature-rich React date picker component library published as `react-datepicker`. It provides a single entry point (`DatePicker`) that supports single date, date range, multiple dates, week, month, quarter, and year picker modes, along with time selection, timezone handling, localization via `date-fns`, and extensive keyboard navigation and ARIA accessibility. Internally, the library uses a class-component architecture with a clear separation of concerns: a `Calendar` component manages month/year navigation, `Month` renders days or month/quarter grids, `Day` handles individual cell rendering with selection and focus management, and `Time`/`InputTime` handle time input. Positioning of the calendar popover is delegated to `@floating-ui/react` via a `withFloating` HOC, and rendering can be redirected to a portal (including shadow DOM) for overlay scenarios. The component exposes over 60 props for customization, including custom input elements, headers, and day rendering. The library is mature and widely adopted, with a comprehensive test suite (Jest + React Testing Library) covering interactions, keyboard navigation, edge cases, and accessibility (axe tests). The build pipeline uses Rollup to produce UMD, CJS, and ES module bundles, and CSS is provided in both standard and CSS Modules variants.
Radicale is a production-grade CalDAV and CardDAV server implemented in Python. It provides a self-hosted solution for managing calendars, address books, tasks, and journals via standard WebDAV, CalDAV, and CardDAV protocols. The system supports multi-user, multi-collection setups with pluggable backends for authentication (htpasswd, LDAP, IMAP, OAuth2, PAM, Dovecot, remote_user), storage (multifilesystem with caching), rights management, sharing (token/map-based), and web UI. It includes a built-in HTTP/HTTPS server with WSGI compatibility, a browser-based management interface, and extensive configuration options for security, performance, and integration with reverse proxies. The architecture follows a modular plugin pattern: each major subsystem (auth, storage, rights, web, hook, sharing, group) defines a base class and is loaded dynamically via a plugin loader. The core application dispatches HTTP requests through a WSGI application class that handles authentication, locking, logging, and profiling. The storage layer uses a mixin-based design to separate concerns (cache, sync, history, lock, etc.) and stores collections as filesystem directories with individual item files. The sharing module provides a REST API for managing shares, including VCF-to-ICS birthday conversion and property overlays. Key features include CalDAV filtering and recurrence expansion, sync-token support, free-busy reports, email notifications via hooks, and a JavaScript frontend for collection and sharing management. The codebase is well-tested with both unit tests (Python) and integration tests (Playwright), and includes CI/CD pipelines for multi-architecture Docker images and PyPI publishing. While primarily an application, it contains reusable data processing logic for iCalendar/vCard parsing and transformation.
This repository is a production-grade React calendar component library (`@ilamy/calendar`) designed as a lightweight (~13 KB gzipped) replacement for FullCalendar. It provides month, week, day, year, and agenda views with drag-and-drop, resource scheduling, RFC 5545 recurring events, iCal export, and internationalization. The core ships no CSS and relies on Tailwind CSS v4 with shadcn/ui tokens, making it themeable and tree-shakeable. Architecturally, the library follows a plugin-first pattern: the core implements a pluggable kernel (`IlamyPlugin` interface) that accepts opt-in plugins for recurrence, agenda, and drag-to-create. Each plugin contributes views, event transformations, mutation scopes, and UI slots through a runtime composer. The state management uses a single `CalendarProvider` context that composes four engine slices (config, navigation, data, interaction). The view system is built on two grid primitives (vertical-grid for time-based layouts, horizontal-grid for date-based layouts) that are shared across all views and test harnesses. The codebase demonstrates strong engineering discipline: a huge unit test suite (995+ tests) with regression pinning against issue numbers, deterministic Playwright E2E tests, a CI pipeline with lint/build/type-check/test gates, and agent-driven code review skills. However, there is some duplication of UI primitives between packages, and the dependency on a custom dayjs wrapper for timezone handling introduces fragility. The library is actively maintained with frequent releases and detailed changelogs.
pandas_market_calendars is a Python library that provides market and exchange trading calendars for over 50 global financial exchanges, including equities, futures, and OTC markets. It generates accurate trading schedules (open/close times, holidays, early closes, late opens, and breaks) as pandas DatetimeIndex objects, enabling developers and quantitative analysts to align time series data, backtest strategies, and check market status. The library is a fork of Quantopian/Zipline's exchange_calendars module, extended with additional calendars, utility functions, and source documentation. Architecturally, the library uses a base MarketCalendar class with a metaclass-based registry pattern that automatically registers all calendar subclasses by name and alias. Individual exchange calendars (e.g., NYSE, CME, LSE, JPX) are implemented as subclasses in the `calendars/` directory, with holiday rules defined in separate `holidays/` modules. Market times are stored in a ProtectedDict (immutable dictionary) to prevent accidental modification. The library also provides a mirror module that wraps calendars from the external `exchange_calendars` package, ensuring backward compatibility. Key entry points include `get_calendar()` to retrieve a calendar instance, `date_range()` to generate intraday timestamps, `merge_schedules()` to combine multiple exchange schedules, and `mark_session()` to classify timestamps into pre-market, regular, and post-market sessions. The library depends on pandas for data structures and timezone handling via zoneinfo, and optionally on exchange-calendars for mirrored calendars. It is designed for production use with extensive test coverage, CI/CD pipelines, and semantic versioning. The library's primary data flow is static: holiday rules and market time definitions are hardcoded in Python code and updated via new releases. There is no runtime data fetching, which ensures reproducibility but requires manual updates when exchanges change their calendars. The changelog shows frequent updates for holiday corrections and new exchange support, indicating active maintenance.
Joda-Time is a mature, comprehensive Java library for date and time manipulation, offering a rich set of immutable and thread-safe classes for instants, partials, intervals, periods, durations, and time zones. It supports multiple calendar systems (ISO, Gregorian, Julian, Buddhist, Coptic, Ethiopic, Islamic, GJ) and provides extensive formatting and parsing facilities, including ISO 8601 and locale-aware period formatting. The library is designed for production use, with a clean interface hierarchy (Readable* and ReadWritable*), a pluggable chronology architecture, a converter pattern for flexible object construction, and a field system that allows modular arithmetic. Despite being 'largely finished' since Java 8's java.time (JSR-310), Joda-Time remains a high-craftsmanship codebase demonstrating immutable value objects, abstract base classes, builder patterns, and internationalization support. Its design influenced java.time, and many components (e.g., the converter set, chronology assembly, type-safe period classes) are reusable patterns for any domain with complex temporal logic.
Rustical is an open-source CalDAV and CardDAV server written in Rust, providing a lightweight, self-hosted alternative for calendar and addressbook synchronization. It implements the core WebDAV extensions (RFC 4791, 6352) with support for CalDAV scheduling, CardDAV group membership, WebDAV Push (web-push) notifications, and a built-in web frontend for management. The architecture is a modular Rust workspace with separate crates for DAV infrastructure, protocol handlers (caldav, carddav), storage abstraction, SQLite backend, XML serialization, OIDC authentication, and a Lit-based web UI. The server exposes RESTful HTTP endpoints via Axum, uses SQLite for persistence with `sqlx`, and supports app tokens, OIDC, and Nextcloud login for authentication. The codebase demonstrates solid engineering with thorough integration tests, snapshot testing, CI/CD pipelines, and a clear separation of concerns. However, it contains some workarounds and TODOs indicating active development rather than a polished final product. The custom XML derive macros and store trait pattern are particularly well-crafted and potentially reusable.
This repository is a .NET library (Ical.Net) that implements the iCalendar specification (RFC 5545) for parsing, manipulating, and serializing calendar data in the ICS format. It provides core types such as Calendar, CalendarEvent, Todo, Journal, FreeBusy, VTimeZone, and Alarm, along with comprehensive support for recurrence rules (RRULE, RDATE, EXDATE), time zone handling via NodaTime, and free/busy computation. The architecture follows an object-oriented design with clear separation of concerns: data types (e.g., CalDateTime, Period, RecurrenceRule), calendar components, serializers (e.g., CalendarSerializer, PropertySerializer), and an evaluation engine for expanding recurring occurrences. The library is production-grade, with extensive test coverage (including a large corpus of ICS fixture files and regression tests for bug fixes), benchmarks for performance, and a logging abstraction. It is not a standalone application but a library designed to be consumed by .NET applications that need iCalendar functionality.
Kurrier is a self-hosted unified communication platform designed to aggregate email, calendars, contacts, and cloud storage into a single workspace. It functions as a multi-tenant SaaS application, supporting various protocols including IMAP/SMTP for email, CalDAV/CardDAV for scheduling and contacts, and WebDAV/S3 for file storage. The system emphasizes data ownership and privacy, allowing users to manage multiple email identities and storage volumes within isolated workspaces. The architecture follows a monorepo structure with a clear separation of concerns. The frontend (`apps/web`) is built on Next.js 16 with React 19, utilizing Server Actions for business logic and a Nitro-based worker (`apps/worker`) for background jobs like IMAP sync and email delivery. Data persistence is handled by PostgreSQL with Drizzle ORM, while Redis manages job queues and caching. The platform integrates with external providers via a strategy pattern, supporting services like Google Workspace, AWS SES, and various SMTP providers. Key components include a robust provider abstraction layer for pluggable email and storage backends, a centralized encryption vault for sensitive credentials, and a standardized Server Action wrapper for consistent error handling. The codebase demonstrates high craftsmanship in its sync logic and multi-tenancy implementation, though it carries some technical debt related to type safety and complex DAV/IMAP state management.
python-o365 is a mature Python library that provides a comprehensive, object-oriented wrapper around the Microsoft Graph API. It enables developers to programmatically access and manage Microsoft 365 services including Outlook email and calendar, OneDrive and SharePoint files, Teams chats and presence, Planner tasks, directory users and groups, and more. The library abstracts OAuth2 authentication (supporting authorization code, public client, and client credentials flows) and handles token refresh, pagination, and API versioning internally. It is designed as a client-side SDK, not a server application, and can be embedded into scripts, web applications (e.g., Flask), or automation workflows.
Vue Cal is a full-featured Vue 3 calendar component library with zero external dependencies beyond Vue itself. It provides multiple views (day, week, month, year, years), event management (create, edit, delete, drag-and-drop, resize), schedules, special hours, extensive localization (50+ languages), dark/light theme via CSS variables, and comprehensive slot-based customization. The library is built entirely with the Composition API and is structured around core composables: `useVueCal` (main state), `useConfig` (prop parsing, locale loading), `useEvents` (event normalization, indexing, overlap detection), `useView` (navigation, cell generation), and `useDragAndDrop` (native HTML5 DnD with cross-instance support). The primary entry point is `src/vue-cal/index.js`, which exports the `VueCal` component, `useLocale` function, and a set of optional Date prototype extensions. Events are passed as an array of objects and reactively rendered; all interactions emit Vue events enriched with context (cell info, cursor position). The library is in active pre-release (v5.0.1-rc.46) with a stable release pending timezone support.
寿ć夊ćĺ (sxwnl) is a comprehensive client-side Chinese astronomical calendar web application. It provides accurate lunar/solar calendar conversion, solar terms (jieqi), planetary and stellar ephemeris, solar/lunar eclipse prediction with interactive maps, rise/set times, and specialized tools (Julian day conversion, Chinese zodiac calculation). The entire application runs in the browser with no server backend, relying on hardcoded astronomical algorithms (VSOP87/ELP-based) and embedded data (city coordinates, historical calendar corrections, star catalogs). The architecture is monolithic: a single HTML page loads multiple JavaScript modules (eph0.js, eph.js, lunar.js, etc.) that manipulate the DOM directly. While the code is functional and accurate for its domain, it suffers from global namespace pollution, outdated browser API usage (VML, deprecated event handling), and a manual Windows-only build process. Despite these issues, individual modules like the ephemeris engine, lunar calendar class, and coordinate transformation utilities are self-contained and could be extracted for reuse in other astronomy or calendar projects.
This repository is a community-maintained knowledge hub for students of the University of London BSc Computer Science programme, providing curated resources, module guides, FAQs, and automation scripts. Although classified as an application due to the presence of a Python script and CI/CD, its primary value is as a documentation and reference repository. The codebase is minimal, consisting of a single utility script (`update_week.py`) with a test suite and a GitHub Actions workflow that weekly updates the current academic week in the README. The bulk of the content is extensive markdown files covering module specifics, kinks (bugs), study tips, software recommendations, and Slack onboarding. The project demonstrates strong community organization, including issue templates, contribution guidelines, and all-contributors integration, but is not a traditional software application or data pipeline.
The Kalendar repository is a Vue 2 plugin that provides a flexible calendar component for managing events. It features week and day views, drag-and-drop event creation, customizable slots for event rendering, and configuration options for appearance and behavior. The component leverages web workers to offload heavy computations (such as generating time slots and constructing events) to maintain UI responsiveness. The architecture follows a modular Vue component structure, with the main container managing state and child components handling specific UI elements (days, cells, events). It uses Vue's provide/inject pattern to pass down configuration and event data, and employs scoped slots for deep customization of event cards. The core library is framework-specific to Vue 2 but isolates concerns like date utilities and worker communication into reusable utilities. Despite its solid foundation, the repository shows signs of technical drift due to its reliance on Vue 2 and outdated build tools (Vue CLI 4, Rollup 1.x, Sass-loader 8.x). The last commit date appears to be in the future (2026-01-21), suggesting a lack of recent maintenance activity, and the project does not include automated tests. However, the utility functions and worker promise wrappers demonstrate reusable, non-obvious patterns that could be extracted for use in other projects.
This repository is a Home Assistant custom integration for displaying ICS (iCalendar) calendars. It fetches calendar data from remote URLs, handles authentication and URL templating, parses ICS files using either the 'recurring_ical_events' or 'ics' library, applies event filtering, and exposes the events as a Home Assistant calendar entity. The architecture follows Home Assistant's custom integration patterns with separate modules for data fetching, parsing, filtering, and entity management. While functional, the project shows signs of stagnation due to expressed maintainer lack of motivation, dependency version pinning, and impending obsolescence from Home Assistant's built-in Remote Calendar integration.