Skip to content
CAI
Software that uses CAICheck a score

acronis/go-cti

66.7

Adequate · 8 November 2026

9.1k

lines of production code

Go

primary language

7

measurements over time

CAI band scale
CAI trend line
CAI lens gauges

What this system is

Features

Initial RAMLx specification and Go embedding

The metadata/ramlx module now includes the core RAMLx specification files (cti.raml, scalar.raml) and a Go package that embeds these resources. This introduces the foundational type definitions for the CTI model, including CTI, CTIWildcard, and CTIAttribute identifiers, along with a comprehensive set of scalar types (strings, integers, floats) and annotations such as resilient, access, and schema that define how CTI entities and their fields are structured and validated.

metadata/ramlx · high confidence

Initial implementation of CLI command structure and package management

This change introduces the foundational structure for the CLI tool, adding command definitions for \init\, \pack\, \pkg\ (with subcommands \get\, \download\, \tidy\), \sync\, \validate\, and placeholders for \deploy\, \env\, \fmt\, \lint\, \rest\, and \test\. It implements core logic for parsing package arguments, managing working directories, and initializing the package manager using Git storage. The \pack\ command specifically supports creating archives in \tgz\ or \zip\ formats, while \pkg get\ and \pkg tidy\ handle dependency installation and synchronization.

cmd/cti/internal · high confidence

Initial release of the CTI library and CLI tool

Introduces the Cross-domain Typed Identifiers (CTI) management tool and library, providing a Go package for parsing CTI expressions (identifiers, queries, attribute selectors) with support for wildcards and dynamic parameters, alongside a CLI for initializing, validating, and packaging CTI bundles. The release includes the MIT license, a Makefile for building and testing, and a .golangci.yml configuration for code quality enforcement.

(repo-wide) · high confidence

Introduce CTI metadata library with entity management, validation, and annotation collection

The metadata package now provides a comprehensive library for parsing, validating, and managing CTI entities and packages. Users can create and manage CTI types and instances via the \EntityType\ and \EntityInstance\ structs, validate data against JSON schemas using \Validate\ and \ValidateBytes\, and retrieve type traits with \GetMergedTraits\. The library includes an \AnnotationsCollector\ to extract metadata annotations from JSON schemas, an \AttributeSelector\ for navigating nested schema structures, and a \MetadataRegistry\ for storing and indexing entities. It also supports legacy source map formats and provides access modifier checks (public, protected, private) to control entity visibility.

metadata · high confidence

Introduce CTI package compatibility checker

Added a new compatibility checking tool in the \metadata/compatibility\ package that validates changes between two CTI packages. The \CompatibilityChecker\ analyzes entity additions, removals, and modifications (including JSON Schema, traits, values, and annotations) to determine if a package update is compatible, reporting results as errors, warnings, or info messages.

metadata/compatibility · high confidence

Introduce CTI package metadata model and parser

This change introduces the core \ctipackage\ library for managing CTI package metadata. It adds a structured \Index\ model (persisted as \index.json\) to track package APIs, entities, assets, and dependencies, along with an \IndexLock\ for dependency resolution. The \Package\ type provides methods to initialize, read, and parse packages, including dependency resolution and RAML/CTI metadata collection. It also includes validation logic for package IDs and dependency names, and a \Validate\ method that parses and validates the package content against the CTI schema.

metadata/ctipackage · high confidence

Introduce RAMLx metadata collector with CTI schema and trait support

Added a new RAMLx collector that processes RAML 1.0 libraries into CTI metadata entities. The collector handles CTI type unwrapping, automatically inserts implicit CTI schema annotations for types inheriting from CTI bases, and supports the resilient and final annotations on instances. It also merges traits from custom shape facets into a unified map and validates traits schemas, ensuring that pattern properties and union types are correctly processed during schema conversion.

metadata/collector/ramlx · high confidence

Introduce extensible metadata validation framework

The metadata/validator package now provides a new MetadataValidator that allows users to register custom validation rules for CTI types and instances via expression-based hooks. This enables flexible, programmatic validation of metadata entities against specific CTI patterns, with support for both type-level and instance-level checks, and integrates with the existing metadata registry for local and global validation contexts.

metadata/validator · high confidence

Introduce metadata archiver with tar.gz and ZIP implementations

Added a new \metadata/archiver\ package that defines an \Archiver\ interface for creating metadata archives, along with concrete implementations for \.tgz\ (in \tgzwriter\) and \.zip\ (in \zippacker\) formats. The implementations support writing individual files, byte buffers, and recursively packing directories while excluding the archive file itself to prevent infinite recursion. This provides a unified way to package metadata artifacts.

metadata/archiver · high confidence

Introduce typed CTI JSON Schema handling and inheritance merging

The metadata/jsonschema package now provides a dedicated, typed Go representation for CTI JSON Schemas (JSONSchemaCTI) that explicitly models CTI-specific annotations such as access modifiers, resilience flags, and localization settings. This change introduces a schema merger that correctly applies inheritance rules—merging properties, required fields, and type constraints from parent to child schemas—and includes a pre-compiled JSON Schema Draft 07 metaschema to enable local validation without network calls. Users benefit from more robust schema composition and validation, ensuring that inherited schema properties are preserved and that schema structures are strictly validated against the Draft 07 standard before use.

metadata/jsonschema · high confidence

Introduction of the metadata collector interface

A new \Collector\ interface and \BaseCollector\ struct have been added to the \metadata/collector\ package. This component serves as the entry point for gathering metadata from a source, utilizing a CTI parser and maintaining a local registry of entities. It also defines a list of annotations (\Reference\ and \Schema\) that are designated to be moved during the collection process.

metadata/collector · high confidence

New CTI metadata collector supporting typed JSON Schema and legacy source maps

A new CTIMetadataCollector has been introduced to handle CTI metadata collection by processing YAML fragments defined via typed JSON Schema. This component parses both CTI Type 1.0 and Instance 1.0 entities, automatically attaching source maps to track original and source paths. It also supports legacy source map formats, ensuring backward compatibility for existing metadata definitions while providing a structured, schema-driven approach to metadata ingestion.

metadata/collector/ctimetadata · high confidence

New file system utilities for secure archive extraction and file operations

The \metadata/filesys\ package now provides a suite of new capabilities for handling file system operations. It introduces secure extraction functions for ZIP and TAR archives (\SecureUnzip\, \SecureUntar\) that include path traversal validation and file size limits to prevent denial-of-service attacks. Additionally, it adds a generic \CopyFS\ function for safely copying directory trees with configurable options for overwriting and permission preservation, as well as utilities for computing file and directory checksums using XXH3, reading/writing JSON files, and basic path manipulation helpers.

metadata/filesys · high confidence

Behavioural changes

CTI CLI restructured with new command set and improved error logging

The cti CLI has been restructured, introducing new commands (init, sync, pack, validate, deploy, env, fmt, info, lint, rest, test) and a common --work-dir flag. Error logging now uses go-stacktrace to capture tracebacks, with an optional --ensure-duplicates flag to deduplicate stack traces in logs.

cmd/cti · high confidence

CTI schema transformer implementation with recursion validation

The metadata transformer now automatically inserts CTI schemas into entity definitions and validates recursive structures to prevent infinite loops. This change ensures that self-recursive CTI types are correctly detected and handled, and that annotations are properly collected for both main and traits schemas. The transformer also resolves CTI type references using a parser and attribute selectors, ensuring that schema references are correctly linked within the metadata registry.

metadata/transformer · high confidence

Packer now supports custom file exclusion and annotation-driven asset inclusion

The metadata packer has been refactored to allow users to control which files are included in the package via a configurable \ExcludeFunction\ callback, enabling custom filtering logic beyond the default behavior. Additionally, the packer now processes entity annotations through a pluggable \AnnotationHandler\ system; the default handler uses this to locate and include asset files referenced by entities, ensuring that related assets are packaged alongside the metadata.

metadata/packer · high confidence

Safe concurrent package installation with process-level locking

The pacman metadata manager now protects its shared package cache directory with an exclusive file lock (using gofrs/flock) during dependency downloads and cache updates. This ensures that multiple processes (such as parallel CI builds) can safely share the same cache without race conditions, preventing corrupted or half-replaced cache entries. The change includes comprehensive concurrency tests verifying that downloads do not overlap and that the lock is correctly released if a process crashes.

metadata/pacman · high confidence

Dependencies

Initialize Go module manifests for CTI components

Added go.mod and go.sum files for the root module, the CLI command (cmd/cti), the metadata library, and the metadata/ramlx sub-module. These manifests establish the project's Go version (1.20 for root, 1.22.6 for sub-modules) and declare direct dependencies including go-raml/v2, go-stacktrace, gojsonschema, and gjson, along with their indirect transitive dependencies.

(dependencies) · 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 62 → 67 (+4.6)
  • Rubric changed (rubric-2026.10.5 → rubric-2026.11.2) — scores are not directly comparable.

Lenses

  • Code Health 65 → 65 (+0.0)
  • Architecture 100 → 100 (-0.0)
  • Maturity 53 → 62 (+8.6)
  • Readiness 65 → 65 (+0.0)
  • Security 85 → 80 (-4.9)
  • Performance 77 → 95 (+17.7)

Resolved (1)

  • Off-boarding risk: anonymized user #1

New (1)

  • Off-boarding risk: anonymized user #1

Changes since last survey

  • 4 commits — 4 feature/other, 0 fixes

By area

  • metadata/go.mod — 2 commits
  • cmd/cti — 1 commit
  • metadata/collector — 1 commit

Notable commits

  • change: ARCH-514 chore(cmd/cti): bump github.com/acronis/go-cti/metadata to v0.62.0
  • change: ARCH-514 chore(metadata): bump github.com/acronis/go-raml/v2 to v2.1.0
  • change: ARCH-514 chore(metadata): bump github.com/acronis/go-raml/v2 to v2.1.1
  • change: ARCH-514 refactor(metadata): use github.com/acronis/go-raml/v2/orderedmap instead of github.com/wk8/go-ordered-map/v2

Written by cca.canine.dev from the codebase's own history, inside the signed delivery this page is composed from.

Survey your own repository

acronis/go-cti 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 8 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 103d98b4d7d0b2db9a0ef2942ec34aed7c5d958d — 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-45ab2cab63de.