Skip to content

Security: Deepkeepai/deepkeep-integrations

SECURITY.md

Security Policy

Reporting A Vulnerability

Do not disclose exploitable vulnerabilities, credentials, customer data, or private deployment information in a public issue or pull request.

If GitHub private vulnerability reporting is enabled for this repository, use the Report a vulnerability option on its Security tab. This document does not assert that private reporting is enabled. If that option is unavailable, contact the repository owner, @gilarel, to arrange a private reporting channel before sending sensitive details. A public request for a private channel must not include the vulnerability details. No response-time or remediation SLA is promised here.

Include the affected integration and package version or commit, dependency/runtime versions, impact, and a minimal reproduction with synthetic data. Share secrets only through an agreed private channel if genuinely needed; normally redact them. If credentials were exposed, revoke or rotate them promptly rather than waiting for a repository change to remove the exposure.

Scope And Known Limits

Reports are welcome for the current monorepo integrations and their packaging/configuration. n8n is permanently standalone at https://github.com/Deepkeepai/n8n-nodes-deepkeep; report current n8n issues through that repository's private reporting guidance. The original eight-import count is historical, not the current-tree scope. This is not a commitment to maintain every historical release. The integrations have independent versions and upstream framework compatibility requirements; consult their READMEs when assessing an affected deployment.

The migration validation recorded a clean gitleaks scan of the full imported 48-commit history, including the four Kong commits. A clean scan is not proof of the absence of secrets or vulnerabilities. The formerly private Kong content was reviewed for public import, and Agentgateway/Kong MIT licensing was explicitly approved; neither constitutes a blanket security certification.

During the 2026-11-05 migration validation, the imported n8n snapshot's unchanged legacy lockfile produced 24 npm vulnerability reports: 11 moderate, 11 high, and 2 critical during npm ci. n8n lint/build passed, but the migration did not remediate those findings or establish that the affected dependencies are safe. npm audit --omit=dev reported zero findings; the reported vulnerabilities were in that snapshot's development dependency graph. These are historical findings, not current-tree dependencies or a fresh standalone audit. Do not confuse a clean secret scan with a clean dependency audit.

Six Python pytest suites passed all 63 tests on Python 3.12 and four Python packages built during migration validation. These checks do not establish a security guarantee, complete runtime coverage, or a supported-version matrix.

The Kong examples are now conservative blocking adapters: redaction/modification, unknown actions, and malformed decisions fail closed; masking is disabled. The embedded functions have executable LuaJIT coverage, but deployed Kong HTTP, template handling, and licensed gateway enforcement are not yet validated. These configurations do not provide content replacement. See the Kong README.

Publishing Boundary

All four Python metadata releases were published after explicit release and environment approval; their artifacts, PyPI attestations, and isolated wheel installations were verified. The last three deployment reviews were submitted through the CLI at the owner's explicit request. Agentgateway image 0.1.0 was subsequently published with matching authenticated digests and passed a separate read-only, network-isolated container health check. Agno's old publisher is disabled; Agentgateway's old CI no longer logs in or pushes, but tests/builds remain active. No npm publication occurred here. The approved five-repository retirement batch is now archived read-only, with Kong still private and source heads unchanged. Archival is not token revocation or licensed gateway validation; see retirement status. Imported nested workflows are inactive in the current tree. Root CI does not publish artifacts.

The root monorepo release workflow is manual-dispatch only, gated by MONOREPO_PUBLISHING_ENABLED=true (absent by default), with independent versions, <integration>/v<VERSION> tags, five release-<integration> job environments, and PyPI OIDC trusted publishing for four Python packages plus Agentgateway GHCR publishing. n8n/npm is excluded; its standalone CI and Release workflows remain active, with no known npm registry-trust migration and no monorepo npm releases. Stop old publishers for in-scope cutovers and configure/verify the new bindings before enabling it. Environment names alone do not establish approval protection. The five in-scope release environments retain reviewer gilarel and a main-only deployment policy; self-review is allowed. Six environments were originally configured; the unused release-n8n environment was removed after the code exclusion merged and zero secrets, variables, and deployments were verified. Registry trust is not established by that GitHub configuration. See the cutover runbook. Historical source tags can contain original publishers outside that gate. Do not create GitHub Releases against imported source tags, add a repository-wide PYPI_API_TOKEN, or grant registry trust to historical workflow identities. See MIGRATION.md for pending operational gates.

There aren't any published security advisories