Skip to content

Security: talvikai/mak4i-protocol

Security

SECURITY.md

Security Policy

Current Scope (Phase 0)

As of Phase 0, this repository contains protocol documentation, the draft specification, artifact metadata (JSON), and the frameworks/wd-docx-framework document-generation tool. There is no hosted API, registry, or production service yet — that begins in Phase 2 (see ROADMAP.md). This policy will be expanded once a hosted service exists.

Reporting a Vulnerability

Please report security vulnerabilities privately via email rather than opening a public GitHub issue so that we have an opportunity to investigate, develop a fix, and coordinate responsible disclosure before details become public.

Please do not disclose suspected vulnerabilities publicly until we have had an opportunity to investigate and coordinate a fix.

Email: hello@talvik.ai

Include:

  • A description of the issue and where it is (file, artifact, or component)
  • Steps to reproduce, if applicable
  • The potential impact, as best you understand it

We aim to acknowledge reports within a reasonable timeframe and will work with you on a fix and disclosure timeline before any public details are shared.

Supported Versions

Given the repository's current stage (Phase 0, pre-1.0 specification), only the latest state of main is supported. There are no maintained release branches yet.

Scope Going Forward

Once Phase 2 ships a hosted reference implementation, this document will be updated to cover:

  • API authentication and authorization
  • Data handling for artifacts submitted to the registry
  • Dependency and supply-chain practices for the SDK and CLI

Until then, if in doubt about whether something is a security concern worth reporting privately versus a general bug worth a public issue, default to reporting it privately at hello@talvik.ai — that costs nothing and avoids any risk of a genuine issue being disclosed publicly before it's understood.


© 2026 Talvik, Inc.

There aren't any published security advisories