The application is a subscription management platform built with Next.js, Prisma, and Better Auth. It allows users to track recurring payments, set up multi-channel notifications (email, push, webhook, ntfy, Discord, Slack), view financial reports, and manage account settings. The system supports multi-currency, timezone awareness, and can be self-hosted via Docker or used as a SaaS with Paddle for payment processing. Architecturally, it follows a client-server model with Next.js App Router, separating concerns into components, lib utilities, API routes, and server actions. The data layer uses Prisma ORM with PostgreSQL, and authentication is handled via Better Auth with multiple providers. Background notification processing is implemented through a cron job hitting the `/api/cron/` endpoint. Key reusable components include a multi-channel notification system, internationalization hooks for language management, and a timezone-aware datetime picker. These components demonstrate encapsulation, minimal internal dependencies, and patterns that could be extracted for use in other projects.
This repository is a web-based management panel for sing-box proxy servers, providing a Gin-based web UI and REST API for configuring inbounds, outbounds, clients, subscriptions, and traffic statistics. It includes custom protocol implementations for many proxy protocols (VMess, VLESS, Trojan, Shadowsocks, Hysteria, TUIC, etc.), session tracking, and subscription generation in multiple formats (plain, JSON, Clash). The architecture is modular with core, service, API, and sub packages, using SQLite for persistence and a cron job system for stats collection and maintenance. The codebase demonstrates strong engineering practices with reusable components like a session registry, graceful QUIC shutdown wrapper, and security middleware. However, it is tightly coupled to sing-box internals, requiring custom manager copies to preserve hot add/remove functionality that upstream dropped, and it has a history of migration-heavy schema evolution. The project is actively maintained with frequent commits, comprehensive testing, and multi-platform deployment support (Linux, Windows, Docker).
This repository implements the GraphQL specification for Swift, providing a complete parsing, validation, and execution engine. It is a library intended to be consumed by server‑side Swift frameworks (e.g., Graphiti, graphql‑vapor) or any Swift project requiring GraphQL support. The architecture follows a layered design: a lexical analyzer and recursive‑descent parser produce an AST (Sources/GraphQL/Language/), a rich type system (Sources/GraphQL/Type/) supports all GraphQL types and directives, a validation layer (Sources/GraphQL/Validation/) implements over 20 spec‑required rules, and an execution engine (Sources/GraphQL/Execution/) resolves queries concurrently. Subscriptions are supported via Swift async sequences (Sources/GraphQL/Subscription/). The library also includes schema construction from SDL, schema printing, and a flexible Map value type for dynamic GraphQL values. In production, a client calls the top‑level `graphql()` function with a schema, a query string, and optional variables. The query is parsed, validated against the schema, and then executed field‑by‑field. Resolvers (provided by the schema) produce results that are serialized into a `GraphQLResult` with proper error handling. The library handles all GraphQL features: object types, interfaces, unions, enums, input objects, custom scalars, directives (`@deprecated`, `@specifiedBy`, `@oneOf`), and persisted queries. The test suite mirrors the reference JavaScript implementation and covers the Star Wars schema, introspection, federation, and edge cases. The codebase is well‑structured and follows best practices for Swift libraries: it uses Swift concurrency, Sendable annotations, and the `swift‑collections` package for ordered dictionaries. Several components are self‑contained and could be reused independently, such as the `Map` dynamic value type, the AST visitor infrastructure, and the printer. However, some deviations from the GraphQL spec remain (e.g., a handful of validation rules are commented out), and there is code duplication between `AnyCoder` and `MapCoder`. Force‑unwraps and some thread‑safety workarounds indicate areas that could be hardened. Overall, the library is production‑ready and actively maintained.
Unicity Sphere is a self-custodial Web3 wallet and agent platform implemented as a React 19 single-page application. It provides wallet creation/restore (with mnemonic backup, password, and file import), direct messaging and group chat (via Nostr relays), a marketplace for agents and apps with reviews and quests, dApp connectivity through the Sphere Connect protocol (iframe agents and popup), and subscription-based quota management for aggregator API access. The architecture is a client-side SPA with a desktop-like shell (tabs, taskbar, wallet panel) using TanStack Query for server state, Framer Motion for animations, and Tailwind CSS for styling. Key entry points include the onboarding flow (CreateWalletFlow), the main wallet panel (WalletPanel), the Connect provider (ConnectProvider), and the desktop layout (DesktopLayout). External dependencies include the @unicitylabs/sphere-sdk for core wallet operations, a local @unicitylabs/sphere-ui package, REST APIs for marketplace and subscription gateway, and Sentry for error monitoring. The codebase has extensive unit and e2e test coverage with a strong focus on security invariants (duplicate send guards, settle shields, origin verification), though a security audit identified 131 findings including unencrypted seed storage and phishing risks. The project is actively maintained with frequent commits and issue triage, but exhibits tight coupling to the SDK and complex state machines that pose maintenance risks.
This repository is a static collection of proxy subscription links and configuration files for V2Ray and Clash proxy clients. It contains a README.md with promotional material for various VPN services, a list of free proxy URIs in v.txt, a Clash YAML configuration file (c.yaml) with hundreds of proxy entries, and a vpn.md with a promotional link. The repository serves as a free source of proxy configurations for circumventing internet censorship. It does not contain any original software code. The architecture is trivial: it is a file-based subscription endpoint. The primary data flow is users downloading these files and importing them into proxy clients.