shortlink-org/shortlink
49.2
Weak · 9 November 2026
24.6k
lines of production code
TypeScript
with Go
6
measurements over time
What this system is
Features
Add Ansible role for deploying the Next.js UI
This change introduces a new Ansible role (\ui-next\) that automates the deployment of the Next.js-based user interface. The role configures Nginx as a reverse proxy to forward traffic to the UI container (running on port 5080) and sets up scheduled cron jobs on gateway hosts to fetch settlement reports and handle retries via API calls. It also includes test infrastructure using Molecule and Travis CI to validate the role's syntax and basic functionality.
ops/ansible/playbooks/roles/ui-next · high confidence
Add Gatling performance testing POC for shortlink service
Introduces a new Proof-of-Concept load testing project in poc/gatling, providing a template for running performance tests against the shortlink service. The package includes simulation scripts for MaxPerformance (ramping up load) and Stability (constant load) tests, along with a Debug simulation for local debugging. It configures the Gatling engine via simulation.conf (defaulting to https://shortlink.best/) and supports logging to console, files, and Graylog, as well as metric export to Graphite/InfluxDB. The project is licensed under Apache 2.0 and includes standard build configuration files.
poc/gatling · high confidence
Add ShortLink Chrome Extension
Introduces a new Chrome extension that automatically parses the current webpage to find all links and allows users to save them for future reference. Built with React and the WXT framework, it provides a user-friendly interface for managing these saved links.
boundaries/link · high confidence
Add cleanup\_pods.sh script for Kubernetes pod maintenance
A new shell script, cleanup\_pods.sh, has been added to the ops/script directory to help manage Kubernetes cluster hygiene. When executed, the script iterates through all namespaces and deletes pods that are in specific undesirable states: Evicted, Error, CrashLoopBackOff, and ContainerStatusUnknown. A README.md file has also been added to document this new utility.
ops/script · high confidence
Add geerlingguy.docker and geerlingguy.pip Ansible roles
The \geerlingguy.docker\ role is now available to install Docker (Community or Enterprise Edition) and Docker Compose on Linux distributions including RHEL/CentOS, Fedora, Debian, and Ubuntu, with support for custom daemon options and user group management. The \geerlingguy.pip\ role is also added to install the Python package manager and install specific Python packages via the \pip\_install\_packages\ variable. Both roles include CI workflows, molecule test configurations, and standard metadata.
ops/ansible/playbooks/roles/geerlingguy.docker · high confidence
Add nginx role with TLS support and optimized configuration
The nginx Ansible role now installs and configures nginx with an optimized configuration (auto worker processes, epoll, gzip) and provisions TLS using bundled self-signed certificates for localhost. The role deploys the certificate and key to /etc/nginx/ssl/ and applies a specific SSL virtual host configuration for ui-next-ssl.local, ensuring secure access for the UI component on gateway hosts.
ops/ansible/playbooks/roles/nginx · high confidence
Add screenshot capture capability for URLs
A new screenshot use case has been introduced in the metadata service, allowing the system to capture images of web pages via a headless browser. Users can now request a screenshot for a given URL; the service navigates to the page using chromedp with a 30-second timeout, waits for the body to load plus an additional second for dynamic content, and saves the resulting image to S3-compatible storage (Minio). The implementation includes a README detailing the UC-2 workflow and handles errors by returning specific domain errors if the screenshot is unavailable or storage fails.
boundaries/metadata/internal/usecases/screenshot · high confidence
Added Cursor AI configuration rules for Go microservices and Git safety
The project now includes AI assistant guidelines to standardize development practices. A new \.cursorrules\ file enforces safe Git operations by requiring explicit user confirmation before pushing changes and mandates English-only commit messages. Additionally, a \go-microservices.mdc\ rule file defines architectural standards for Go services, specifying the use of Clean Architecture, interface-driven design, explicit error handling, and OpenTelemetry for distributed tracing and observability.
.cursor · high confidence
Added GitLab Container Registry authentication certificate and key
New certificate and private key files for GitLab Container Registry authentication have been added to the operations directory. This enables secure authentication for the registry service using the provided GitLab-specific credentials.
ops/cert/gitlab · high confidence
Added Nginx configuration for the API boundary
This change introduces the Nginx configuration files for the API service, including the main \nginx.conf\ with optimized worker settings, caching, and JSON logging; a local server block in \api.local\ that proxies requests to the backend API on port 7070; and template files for security headers (\default.conf\) and SSL/TLS settings (\ssl.conf\). These configurations enable the API to handle HTTP traffic with proper proxying, caching, and security headers, while also providing the structure for future SSL support.
ops/dockerfile/boundaries/api · high confidence
Added POC scripts for GKE cluster creation and Protobuf installation
New scripts have been added to the POC directory to assist with environment setup. The \k8s\_create\_cluster\_on\_gcloud.sh\ script provides a command to create a Kubernetes cluster on Google Cloud (GKE) with specific configurations for the 'shortlink' project, including node counts, machine types, and enabled addons. Additionally, \install-protobuf.sh\ automates the installation of Protocol Buffers on Linux and macOS systems.
poc/scripts · high confidence
Added X/Open XA distributed transaction proof-of-concept with DTM example
This change introduces a new proof-of-concept directory for X/Open XA distributed transactions. It includes documentation on the advantages and disadvantages of XA compared to SAGA and TCC patterns, and provides a runnable example using the DTM (Distributed Transaction Manager) service. The example demonstrates a saga-style transaction flow with compensation logic using a PostgreSQL database and Docker Compose for local setup.
poc/xa · high confidence
Added kube-secret-fetcher script to fetch Kubernetes secrets into .env files
A new Node.js utility script has been added to the common scripts area that retrieves a specific key from a Kubernetes secret and writes its value to a local .env file. Users can run the script via npm, providing the namespace, secret name, secret key, and the target environment variable key as arguments, allowing for easier integration of Kubernetes secrets into local development or deployment configurations.
boundaries/common/script · high confidence
Initial ClusterFuzzLite integration for automated fuzzing
Added configuration files to enable automated fuzzing via ClusterFuzzLite. The new Dockerfile sets up the Go build environment, project.yaml defines the Go language, libfuzzer engine, and x86\_64 architecture, and build.sh installs the necessary fuzzing tools and compiles the FuzzBatch function in the pkg/batch package.
.clusterfuzzlite · high confidence
Initial ML model training script and CI pipeline configuration
Added a new machine learning proof-of-concept under \poc/ml-diff\ that includes a GitLab CI pipeline definition (\ml-diff.yml\) to trigger a manual release stage, a Python training script (\train.py\) using scikit-learn's RandomForestClassifier to compute accuracy and generate a confusion matrix, and supporting project files (Makefile, .gitignore, README) to manage dependencies and build tasks.
poc/ml-diff · high confidence
Initial Terraform infrastructure configuration for PostgreSQL and Kubernetes
Added initial Terraform configuration files to the ops/terraform directory, establishing the foundation for managing infrastructure as code. The setup defines required providers for PostgreSQL and Kubernetes, configures a PostgreSQL provider to connect to a local 'postgres' host, and provisions two specific databases ('my\_db' and 'my\_db2'). It also includes variable definitions for database credentials and enforces a minimum Terraform version of 1.16.0, alongside a .gitignore file to exclude local state and configuration artifacts from version control.
ops/terraform · high confidence
Initial Vagrant-based local Kubernetes cluster setup
The \poc/vagrant\ directory now contains a complete configuration for spinning up a local Kubernetes cluster using Vagrant, VirtualBox, and Ansible. Users can define the number of VM instances and their resources (CPU, memory) via a new \.env\ file, while the \Vagrantfile\ provisions Ubuntu Bionic VMs with forwarded ports and private networking. A \Makefile.mk\ provides a convenience target to trigger the Ansible playbook that initializes the cluster using kubeadm.
poc/vagrant · high confidence
Initial commit of the boundaries/ui frontend application
The UI boundary has been introduced as a new Next.js application. This includes the foundational project structure, configuration files (such as .env for development/production, .gitignore, and Prettier settings), and documentation. The setup establishes the frontend environment using Next.js, TailwindCSS, and TypeScript, with integration points defined for the Shortlink API, Sentry monitoring, and Firebase services.
boundaries/ui · high confidence
Initial documentation and architecture decisions for the API Gateway
Added the initial project documentation for the API Gateway service, including a README outlining supported protocols (HTTP REST, GraphQL, WebSocket, gRPC-gateway, and CloudEvents) and a public logo. Introduced Architecture Decision Records (ADRs) detailing the service's inception, the strategy to split the gateway into separate services per protocol, and the addition of WebSocket support for real-time bidirectional communication.
boundaries/api/api-gateway · high confidence
Initial mobile client scaffolding and E2E testing setup
The ShortLink mobile application has been initialized as an Expo-based app within an Nx monorepo. This change introduces the core application structure, including navigation with React Navigation and a shared UI carousel component. It also establishes a comprehensive end-to-end testing infrastructure using Detox, with configurations for iOS and Android simulators/emulators, alongside unit testing via Jest and React Native Testing Library.
(repo-wide) · high confidence
Initial release of the BFF Link service
Introduces the new Backend-for-Frontend (BFF) service for the Link domain, providing a dedicated API gateway for web clients. The service aggregates and transforms data from the Link, Billing, and Identity services, handling authentication via Ory Kratos and authorization via SpiceDB. It includes a Go-based HTTP API using the chi router, Redis caching, and comprehensive documentation (C4 diagrams, Swagger, Postman collections) to support the web application's interaction with the backend microservices.
boundaries/bff · high confidence
Initial release of the Metadata service boundary
This change introduces the new Metadata service boundary, a component designed to enrich link information by fetching metadata and generating screenshots upon link creation. The implementation includes the Go application entry point, dependency injection wiring, and configuration via the go-sdk. It also establishes the project structure with ADRs (Architecture Decision Records), contributing guidelines, and environment documentation, alongside Protobuf definitions for its API contract.
boundaries/metadata · high confidence
Introduce common Helm chart for shared infrastructure services
This change adds a new Helm chart (version 0.2.3) in the common operations area to manage shared infrastructure dependencies, specifically bundling the shortlink-template (v0.12.6) and Redis (v25.3.11) charts. The chart configures Redis with metrics and Prometheus integration enabled by default, while disabling persistence and authentication for the default deployment, and defines a standard PriorityClass for ArgoCD manifests.
boundaries/common/ops/common · high confidence
Introduce dedicated Dockerfiles and configuration for the support platform boundary
This change adds the containerization artifacts for the support platform boundary, including \support.Dockerfile\ (based on PHP 8.5 FPM Alpine) and \support-proxy.Dockerfile\ (based on nginx 1.31 Alpine). It introduces specific configuration files: an nginx \default.conf\ that serves PHP via FastCGI on port 8080 with an 8MB request body limit and exposes \/live\ and \/ready\ health endpoints, and PHP INI files (\opcache.ini\, \status.ini\) that enable OPcache with specific memory settings and expose the PHP-FPM status page on localhost. The setup also integrates Pyroscope for observability within the PHP container.
ops/dockerfile/boundaries/platform/support · high confidence
Introduce metadata parsing use case with HTML extraction
Added a new parsers package within the metadata boundary that implements application logic for extracting metadata from URLs. The \Set\ use case fetches HTML content via an HTTP client, parses it using goquery to extract description and keywords meta tags, and persists the result to the metadata store. A corresponding \Get\ use case retrieves existing metadata by hash, handling not-found errors appropriately. The package includes a README documenting the interaction flow and unit tests verifying the extraction and storage behavior.
boundaries/metadata/internal/usecases/parsers · high confidence
New CQRS-based link management use case
A new CQRS implementation for link management (UC-02) has been added to the link boundary. This introduces a dedicated service that handles link creation, updates, and deletion by subscribing to domain events (LinkCreated, LinkUpdated, LinkDeleted, MetadataExtracted) via Watermill and persisting them to a CQRS store, while read operations (Get, List) are executed through a separate query store using a saga pattern. The implementation includes specific error handling for retryable vs. non-retryable errors and trace context propagation from Kafka metadata.
_boundaries/link/internal/usecases/link\cqrs · high confidence
New Danger CI rules and systemd service configuration for the POC
This change introduces a new Danger integration for merge request validation within the \poc/danger\ directory. It adds specific rules to enforce commit message standards (including squash handling and commit count limits), automatically assign reviewers and maintainers, manage labels (including inheritance from closed issues), and ensure merge requests have titles, descriptions, and milestones. It also includes a CI job definition (\danger.yml\) to run these checks. Additionally, the \poc/systemd\ directory adds configuration files for a systemd socket-activated service (\api.service\ and \api.socket\) to handle API deployments with zero-downtime restarts.
poc/danger, poc/systemd, ruby · high confidence
New Dockerfile for the shortdb boundary service
A new Dockerfile and .dockerignore have been added for the shortdb service, establishing a multi-stage build that compiles the Go application using golang:1.27-alpine and runs it on debian:13.6. The build enables several Go experimental features (rangefunc, newinliner, arenas, cgocheck2, greenteagc, jsonv2), installs liburing-dev for io\_uring support, and configures the container to expose a health check on port 9090.
ops/dockerfile/boundaries/shortdb · high confidence
New Dockerfiles for marketing referral and notification bot services
Added dedicated Dockerfiles and corresponding .dockerignore files for the marketing referral service (Python-based, exposing ports 8000 and 9090) and the notification bot service (Java-based, exposing port 9090). These files establish isolated build contexts and runtime environments for these specific boundary components, including health checks and user permission settings.
ops/dockerfile/boundaries/marketing · high confidence
New Kubernetes development and operations tooling
This change introduces a comprehensive set of Makefile targets and configuration files under ops/Makefile/k8s to streamline local Kubernetes development and Helm chart management. It adds support for Minikube (with tracing and audit logging enabled), Skaffold for rapid iteration, and Telepresence for local debugging. Helm workflows are enhanced with automated documentation generation, schema validation, and chart testing (ct) via Kind. Additionally, Velero backup/restore capabilities are included, and the kubectl apply behavior is configured to use the safer, more performant pruning mechanism introduced in Kubernetes 1.27.
ops/Makefile/k8s · high confidence
New commit message linting and helper utilities in the Danger POC
This change introduces a new \CommitLinter\ class within the \poc/danger/danger\ proof-of-concept area, enabling automated validation of commit messages against specific style rules. The linter checks for subject length (warning at 50 chars, error at 72), word count minimums, capitalization, trailing periods, and the presence of blank line separators. It also enforces that large changes (over 3 files or 30 lines) include detailed descriptions in the commit body. Additionally, the commit message content is scanned to discourage the use of Markdown/Unicode emojis and short references (like \\#123\), recommending full URLs instead. Supporting this functionality are new \EmojiChecker\ and \Helper\ modules that provide utilities for detecting emoji usage, categorizing changed files (e.g., docs vs. backend), and handling HTTP requests for external data.
poc/danger/danger · high confidence
New modular docker-compose structure for development environments
The development environment setup has been reorganized into a modular structure under \ops/docker-compose/application\, introducing dedicated configuration files for each service boundary. This change adds specific docker-compose definitions for the API, Link, Metadata, Logger, and Support services, alongside comprehensive configurations for authentication and authorization components including Ory Kratos (with TOTP and OIDC providers), Keycloak (with Grafana integration and realm imports), Hydra, Keto, and SpiceDB. The new layout also includes a README specifying Docker 24.0.6+ and Compose v2.22.0+ requirements, and enables watch-mode development rebuilds for Go and Next.js boundaries.
ops/docker-compose · high confidence
New platform boundary Dockerfiles for Backstage, CSI, Go WASM, and Landscape
This change introduces new Dockerfile definitions for four platform components, organizing them under the \ops/dockerfile/boundaries/platform\ directory. The Backstage service is now built using Node.js 24.15.0 with a multi-stage build that includes Python and SQLite dependencies for its backend. The CSI component is compiled from Go 1.27-alpine, exposing metrics on port 9090. A new Go WASM build targets the wasip1 architecture to produce a WebAssembly plugin. Finally, the Landscape service is containerized using the \ghcr.io/nginx/nginx-unprivileged:1.31-alpine-otel\ image, serving static content generated by the \landscape2\ builder, complete with a custom NGINX configuration for health checks and gzip compression.
ops/dockerfile/boundaries/platform · high confidence
Proof-of-concept CEL evaluation service for JWT validation
Adds a new proof-of-concept service in the \poc/cel\ directory that exposes an HTTP endpoint (\POST /evaluate\) to validate JSON Web Tokens using Common Expression Language (CEL). The service loads rule definitions from the \rules/\ directory (specifically \jwt\_audience.cel\ and \jwt\_exp.cel\) and evaluates them against provided JWT claims and timestamps, returning a JSON map of rule names to boolean results. This allows users to test CEL-based validation logic for audience and expiration checks via a simple API.
poc/cel · high confidence
Proxy service scaffolding with Clean Architecture, Zero-Trust permissions, and Vitest integration
The proxy boundary now includes a complete project structure enforcing Clean Architecture through TypeScript path aliases and ESLint boundary rules, alongside a \permissions.json\ file that implements Node.js Permissions API for Zero-Trust security in production. The setup integrates Vitest with Testcontainers for stable integration testing, configures pnpm 11 for dependency management, and defines the OpenAPI specification for the redirect and health-check endpoints.
boundaries/proxy · high confidence
Repository initialization with DDD-first monorepo structure and developer tooling
The repository is initialized with a Domain-Driven Design (DDD) monorepo structure, defining bounded contexts (link, metadata, bff, proxy, ui, mobile, chrome-extension) under the \boundaries/\ directory. This change introduces comprehensive developer tooling and configuration, including a \.code-workspace\ file for VS Code, a \.golangci.yml\ linter configuration (v2), a \.pre-commit-config.yaml\ for multi-language checks, and a \.env.example\ detailing configuration for stores (Postgres, MongoDB, Redis, etc.), APIs, and observability. It also establishes project governance and documentation standards through files like \AGENTS.md\ (providing DDD operating guidelines for coding agents), \CONTRIBUTING.md\, \GOVERNANCE.md\, \ADOPTERS.md\, and \SECURITY.md\, alongside CI/CD configurations for Helm chart testing (\ct.yaml\) and Codecov.
(repo-wide) · high confidence
Architecture
Application layer refactored to Clean Architecture with Use Case pipeline and interceptors
The proxy's application layer has been restructured to enforce Clean Architecture principles, introducing a formal Use Case pattern with dedicated request/response DTOs (e.g., GetLinkRequest, GetLinkResponse) and a central UseCasePipeline. This pipeline supports cross-cutting concerns via interceptors, including Logging (with sensitive data redaction), Metrics (OpenTelemetry integration), and Authorization. The refactoring also adds a centralized error handling strategy with specific exception types (ApplicationError, ValidationError, InfrastructureError) and an EventDispatcher for domain events, replacing the previous ad-hoc service implementations.
boundaries/proxy/src/infrastructure · high confidence
Introduce boundary-specific Dockerfiles for Shop services
The build infrastructure for the Shop boundary has been reorganized by introducing dedicated Dockerfiles and corresponding .dockerignore files for the admin, BFF, and UI components. The admin service now uses a Python 3.14-slim base with the uv dependency manager, the BFF service is containerized using Node.js 24.15.0-alpine for the WunderGraph stack, and the UI service utilizes Node.js 24.15.0-alpine with Next.js 15.0.0-rc.0. These changes replace previous monolithic or less structured build definitions with isolated, optimized build contexts for each service.
ops/dockerfile/boundaries/shop · high confidence
Behavioural changes
10 commits (0 fixes) modifying boundaries/metadata/internal/usecases/metadata
A change to existing behaviour in boundaries/metadata/internal/usecases/metadata — 10 commits, 2 files: “refactor: remove unused eventBus and registry fields from link\_cqrs.Service”; “improve observability”; “bff: refactoring”; and 6 more.
boundaries/metadata/internal/usecases/metadata · medium confidence · unverified
Link access control now uses email-based allowlists for private links
The link use cases have been refactored to implement stricter privacy controls. When accessing a private link, the system now retrieves the user's email via the Kratos Admin API and verifies it against the link's configured allowlist, denying access if the email is missing or not permitted. Public links continue to allow immediate access without permission checks. Additionally, the Add, Delete, and List operations now utilize a saga pattern to coordinate store persistence, SpiceDB permission management, and event publishing, ensuring consistent state and improved observability through OpenTelemetry tracing.
boundaries/link/internal/usecases/link · high confidence
Makefile refactored into modular task files
The monolithic Makefile has been split into separate modular files (ansible.mk, cert.mk, cli.mk, common.mk, dev.mk, docker.mk, docs.mk, git.mk, go.mk, terraform.mk, vagrant.mk) to improve maintainability and organization. This change introduces dedicated targets for Ansible operations, certificate generation via cfssl, CLI building and documentation, Docker configuration and login, Go tooling and linting, Terraform initialization and application, Vagrant VM management, and Git configuration. The refactoring also adds a 'confirm' target for safety checks and updates the Go linter version to v1.64.6.
ops/Makefile · high confidence
Nginx template now supports QUIC and HTTP/3
The Nginx configuration template for the UI has been updated to enable QUIC and HTTP/3 protocols alongside standard SSL and HTTP/2. This change allows the UI service to utilize the newer HTTP/3 protocol for improved performance and connectivity, particularly in challenging network conditions, by listening on port 443 with the quic and reuseport directives.
ops/ansible/playbooks/templates · high confidence
Proxy Helm chart updated to use HTTPRoute and enable Kafka
The proxy Helm chart (version 0.3.2) has been refactored to replace the previous Ingress-based networking with HTTPRoute/GRPCRoute configuration, including a No-Vary-Search header filter for URL rewrite rules. Additionally, the proxy service now defaults to using Kafka as the message queue backend (MQ\_ENABLED: true, MQ\_TYPE: kafka) and includes updated OpenTelemetry exporter endpoints for metrics and logs. The chart also depends on the shortlink-template version 0.12.6.
boundaries/proxy/ops/proxy · high confidence
Refactored proxy dependency injection to use Awilix CLASSIC mode and explicit injection
The proxy service's dependency injection setup has been restructured into a modular composition root using Awilix. The container now explicitly sets InjectionMode.CLASSIC to prevent unintended property resolution, and uses explicit .inject() calls for components like ProxyController, RedisLinkCache, and the message bus/event publisher factories. This change ensures that dependencies are resolved correctly, particularly for the ProxyController and dynamic message bus selection (Kafka vs RabbitMQ) based on the MQ\_TYPE environment variable, resolving previous DI container issues.
boundaries/proxy/src/di · high confidence
Test coverage
Added E2E integration tests for proxy redirect flows; Added unit tests for EventDispatcher and LinkRedirectedEventHandler; Added unit tests for GetLinkByHash and PublishEvent use cases.
Dependencies
1271 commits updating dependencies (33 manifests)
A dependency / build maintenance change in (dependencies) — 1271 commits (563 fixs), 33 files: “upd deps”; “fix(deps): update opentelemetry-js-contrib monorepo (\#22470)”; “refactoring”; and 1069 more (refs \#22470, \#15674, \#22146, \#22622, \#22582, …).
(dependencies) · high confidence · unverified
Initial Gatling SBT project configuration
The \poc/gatling/project\ directory now contains the foundational build configuration for the Gatling proof-of-concept. This includes \build.properties\ setting SBT to version 1.13.0, \plugins.sbt\ adding the \gatling-sbt\ plugin (v4.18.1), and \Dependencies.scala\ defining core dependencies: Gatling Highcharts and Test Framework (v3.7.6), Logback GELF (v4.0.2), Gatling Picatinny (v0.10.0), and Janino (v3.1.6).
poc/gatling/project · high confidence
Written by cca.canine.dev from the codebase's own history, inside the signed delivery this page is composed from.
How this codebase got here
Score
- CAI 51 → 49 (-1.8)
- Rubric changed (rubric-2026.10.5 → rubric-2026.11.2) — scores are not directly comparable.
Lenses
- Code Health 68 → 68 (-0.0)
- Architecture 74 → 72 (-1.9)
- Maturity 59 → 90 (+31.5)
- Readiness 35 → 29 (-6.4)
- Security 72 → 73 (+0.6)
- Domain Modelling 81 → 64 (-17.1)
- Accessibility 64 → 63 (-1.1)
- Performance 83 → 97 (+14.3)
Resolved (110)
- ADR has no Consequences section (docs/ADR/decisions/0028-go-and-debug-concurrency.md)
- Checkable ADR rule enforced only by prose: 16. Adopting Domain-Driven Design (DDD) and Clean Architecture Principles (docs/ADR/decisions/0016-use-domain-driven-developer.md)
- Consequences are present but only benefit bullet points; no trade-offs (e.g. vendor lock-in to Storybook or component selection) and no link to the actual UI-kit implementation (docs/ADR/decisions/0040-ui-kit.md)
- Consequences/trade-offs are deferred and the link ('structured-logging.html') does not appear to explain any real trade-off (e.g. performance cost of structured logs vs human-readable output) (docs/ADR/decisions/0010-logger-format.md)
- Context and consequences are both cited to an external source (Michael Nygard's blog + adr-tools repo), leaving the ADR itself uninformative and its own rationale buried in links (docs/ADR/decisions/0001-record-architecture-decisions.md)
- Context and decision are both single words ('We want to know product metrics by each services' / 'We made grafana dashboard for product-metrics by each services') with no consequences; the Consequences section is cut at "2. Functional" before any real trade-offs (docs/ADR/decisions/0008-product-metrics-by-services.md)
- Context and decision are identical ("We want to have a monorepository for the platform."), with no context/problem and no consequences (docs/ADR/decisions/0012-use-monorepository.md)
- Context and decision are present but the consequences section is a single one-line statement ('We will be able to make our UI accessible for people with disabilities.') referencing no concrete trade-offs (e.g. performance cost of prefers-reduced-transparency), leaving only an aspirational claim (docs/ADR/decisions/0039-ui-accessibility.md)
- Context is a one-line rationale ('We use tracing and logging systems to track application events, and we need to set naming standards for spans and their attributes') with no trade-offs or alternative framing (docs/ADR/decisions/0009-naming-spans-and-attributes.md)
- Context is a single sentence ('We want to use integration tests to verify the correctness of our code.') and decision restates 'We will use k6' with no rationale; consequences are boilerplate install commands (go install + xk6 build) plus one plugin link (docs/ADR/decisions/0020-k6.md)
- Context is excellent but consequences are restated (e.g. 'We use the [4C model] for the documentation of the application architecture.') rather than being a new consequence (docs/ADR/decisions/0011-application-architecture-documentation.md)
- Context is thin ("This ADR addresses the need to standardize our code style tool, considering efficiency and developer experience."), decision is a one-line rationale with no alternatives considered, and consequences are only a single sentence without trade-offs (docs/ADR/decisions/0032-python-code-style-selection.md)
- Critical CVE: [GHSA redacted] (boundaries/mobile/pnpm-lock.yaml)
- Critical CVE: [GHSA redacted] (boundaries/ui/pnpm-lock.yaml)
- Critical CVE: [GHSA redacted] (boundaries/ui/pnpm-lock.yaml)
- Decision and consequences are cut off mid-body before the visible elements (context plus Docs) are fully shown (docs/ADR/decisions/0004-use-uuid-as-primary-keys.md)
- Duplicated block (10 lines × 2) (boundaries/link/internal/usecases/link/add.go)
- Duplicated block (11 lines × 2) (boundaries/link/internal/infrastructure/repository/crud/dgraph/dgraph.go)
- Duplicated block (13 lines × 2) (boundaries/link/internal/usecases/link/error.go)
- Duplicated block (14 lines × 2) (boundaries/link/internal/infrastructure/repository/cqrs/query/postgres/get.go)
- …and 90 more
New (153)
- ADR considers only one option (docs/ADR/decisions/0031-js-package-manager.md)
- Classify ADR enforcement: 1. Adopting Expo Monorepo with Nx for ShortLink Service Client (boundaries/mobile/docs/ADR/decisions/0001-init.md)
- Classify ADR enforcement: 1. Connect Interceptors для cross-cutting concerns (boundaries/proxy/docs/ADR/decisions/0001-connect-interceptors.md)
- Classify ADR enforcement: 1. Init (boundaries/link/docs/ADR/decisions/0001-init.md)
- Classify ADR enforcement: 1. Init API Gateway Service (boundaries/api/api-gateway/docs/ADR/decisions/0001-init.md)
- Classify ADR enforcement: 1. Init Link Boundary context (boundaries/common/docs/ADR/decisions/0001-init.md)
- Classify ADR enforcement: 1. Introduce a BFF Service for the Web Application (boundaries/bff/docs/ADR/decisions/0001-init.md)
- Classify ADR enforcement: 1. Record architecture decisions (docs/ADR/decisions/0001-record-architecture-decisions.md)
- Classify ADR enforcement: 10. logger format (docs/ADR/decisions/0010-logger-format.md)
- Classify ADR enforcement: 11. Application architecture documentation (docs/ADR/decisions/0011-application-architecture-documentation.md)
- Classify ADR enforcement: 12. Use monorepository (docs/ADR/decisions/0012-use-monorepository.md)
- Classify ADR enforcement: 13. Enhancing Security Measures (docs/ADR/decisions/0013-security.md)
- Classify ADR enforcement: 14. Standardizing Observability Tools (docs/ADR/decisions/0014-observability.md)
- Classify ADR enforcement: 15. authentication (docs/ADR/decisions/0015-authentication.md)
- Classify ADR enforcement: 16. Adopting Domain-Driven Design (DDD) and Clean Architecture Principles (docs/ADR/decisions/0016-use-domain-driven-developer.md)
- Classify ADR enforcement: 17. Profile-guided optimization (docs/ADR/decisions/0017-profile-guided-optimization.md)
- Classify ADR enforcement: 18. Standard Metrics for Services using Prometheus (docs/ADR/decisions/0018-service-metrics.md)
- Classify ADR enforcement: 19. front-end testing (docs/ADR/decisions/0019-front-end-testing.md)
- Classify ADR enforcement: 2. C4 Model for Link boundary context (boundaries/common/docs/ADR/decisions/0002-c4-model.md)
- Classify ADR enforcement: 2. C4 System (boundaries/metadata/docs/ADR/decisions/0002-c4-system.md)
- …and 133 more
Changes since last survey
- 31 commits — 20 feature/other, 11 fixes
By area
- boundaries/ui — 9 commits
- boundaries/proxy — 6 commits
- boundaries/mobile — 5 commits
- boundaries/chrome-extension — 4 commits
- boundaries/api — 3 commits
- .github/workflows — 2 commits
- boundaries/link — 1 commit
- poc/ml-diff — 1 commit
Notable commits
- fix: fix(deps): update dependency @next/env to ^16.4.3 (#23051)
- fix: fix(deps): update dependency @next/env to ^16.4.5 (#23111)
- fix: fix(deps): update dependency @pyroscope/nodejs to v0.7.1 (#23024)
- fix: fix(deps): update dependency compression to v1.8.2 [security] (#23074)
- fix: fix(deps): update dependency jspdf-autotable to ^5.0.9 (#23094)
- fix: fix(deps): update dependency numpy to v2.5.4 (#23095)
- fix: fix(deps): update dependency react-native-paper to ^5.15.4 (#23112)
- fix: fix(deps): update dependency react-redux to ^9.3.1 (#23036)
- fix: fix(deps): update dependency uuid to ^14.0.3 (#23096)
- fix: fix(deps): update expo monorepo (#23097)
- fix: fix(deps): update module go.opentelemetry.io/contrib/instrumentation/net/http/otelhttp to v0.72.0 (#23049)
- change: chore(deps): update dependency @prisma/client to v7.10.1 (#23108)
- change: chore(deps): update dependency @testing-library/user-event to ^14.6.8 (#23087)
- change: chore(deps): update dependency @types/lodash to ^4.17.27 (#23088)
- change: chore(deps): update dependency @vitejs/plugin-react to ^6.1.2 (#22989)
- change: chore(deps): update dependency eslint-plugin-prettier to ^5.5.7 (#23089)
- change: chore(deps): update dependency fastify to v5.12.6 [security] (#23068)
- change: chore(deps): update dependency metro-resolver to ^0.88.0 (#22656)
- change: chore(deps): update dependency nx to v22.7.10 [security] (#23069)
- change: chore(deps): update dependency postcss to ^8.5.31 (#23059)
- …and 11 more
Architecture
- Containers 0 added · 0 removed · contexts 0 added · 2 removed · edges 0 added · 0 removed
Removed bounded contexts (2)
- github.com/shortlink-org/shortlink/boundaries/link
- github.com/shortlink-org/shortlink/boundaries/metadata
Written by cca.canine.dev from the codebase's own history, inside the signed delivery this page is composed from.
Survey your own repository
shortlink-org/shortlink was measured the same way every project in this corpus was: the same rubric, at a pinned commit, with the result published in full. Point a surveyor at a repository you know and see whether you agree with it.
About this page
- The score is its most recent published measurement, taken on 9 November 2026 at a pinned commit. It is not a live figure and does not change until the project is measured again.
- Measured at commit 587f6fd9360e6632e8b1a81878bc2215792c25f5 — the exact code this score is about.
- Scored under rubric-2026.11.2 — the same rubric and the same method as every other entry in this index.
- Measured by Canine Code Analyzer (cca.canine.dev) using cca measure-2026.11.3+preprod-bb0cb800cd0f.