This repository has been archived on 2026-11-17. You can view files and clone it, but cannot push or open issues or pull requests.
caelum0x 49b183818c Unify gitgram + aitimemachine into the monorepo (de-submodule) and merge vendored engines
Convert gitgram/ and aitimemachine/ from embedded git repos (which showed as
opaque submodule gitlinks on GitHub) into fully-tracked first-party content.

AITM now merges its 7 vendored repos as first-party engines:
- memory: beads (Go task DAG) + context7 (docs SDK), unified into saved_contexts
- git: vendored C git (bundled binary) + gitnexus (in-process code intelligence)
- agentic: a2a (@a2a-js/sdk) + pal (AITM-managed Python subprocess)

Includes the full session's product build: Gitgram web/mobile/backend features,
AITM website/CLI/MCP, the unified memory layer, engine build tooling
(scripts/build-engines.sh, Dockerfile, CI), docs (README, ENGINES.md, ARCHITECTURE.md),
and extensive test suites.

Build artifacts, node_modules, external/, and gemini-cli are gitignored.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-23 14:14:09 +03:00

1.6 KiB

Security Policy

Supported Versions

The following versions of Context7 MCP are currently supported with security updates:

Version Supported
1.0.x ✅

We recommend always using the latest version (@upstash/context7-mcp@latest) to ensure you have the most recent security patches and features.

Reporting a Vulnerability

We take the security of Context7 seriously. If you discover a security vulnerability, please report it responsibly.

How to Report

What to Include

  • A description of the vulnerability
  • Steps to reproduce the issue
  • Potential impact of the vulnerability
  • Any suggested fixes (optional)

What to Expect

  • Initial Response: We aim to acknowledge your report within 48 hours
  • Status Updates: You can expect updates on the progress every 5-7 business days
  • Resolution Timeline: We strive to resolve critical vulnerabilities within 30 days

After Reporting

  • If the vulnerability is accepted, we will work on a fix and coordinate disclosure with you
  • We will credit reporters in our release notes (unless you prefer to remain anonymous)
  • If the report is declined, we will provide an explanation

Please Do Not

  • Disclose the vulnerability publicly before we have addressed it
  • Exploit the vulnerability beyond what is necessary to demonstrate it