Skip to content

Graph-Native Infrastructure for Context and Accountable AI Systems

1.7 KB
Raw Blame
# OSV-Scanner ignore config (also consumed by OpenSSF Scorecard's
# "Vulnerabilities" check, which reports advisories found in this repo's
# dependency manifests via https://osv.dev).
#
# See https://github.com/google/osv-scanner#ignore-vulnerabilities-by-id for
# the file format.

# opentelemetry-api: TraceState.from_header parses an inbound W3C tracestate
# header in O(N^2) time, fixed in 1.45.1. Pinned at 1.43.0 in requirements-ci.txt
# and uv.lock (google-adk caps opentelemetry-api, at <=1.44 as of 2.13.0) and at
# 1.37.0 in .github/requirements/security-scan-tools.txt (semgrep pins ~=1.37.0).
# Semantica never imports opentelemetry, its google-adk integration runs no HTTP
# server, and the semgrep CLI handles no inbound requests, so no inbound
# tracestate header is parsed. See the matching IGNORED_VULN_IDS entry in
# .github/workflows/security-scan.yml.

[[IgnoredVulns]]
id = "GHSA-xcq7-p3pf-p88h"
ignoreUntil = 2027-01-23
reason = "opentelemetry-api <1.45.1, capped by google-adk and semgrep; no inbound tracestate parsing. See security-scan.yml."

# ---------------------------------------------------------------------------
# chromadb / json-repair (previously pulled in transitively by an opt-in
# `crewai` extra) are no longer resolvable at all: the `crewai` extra was
# removed from pyproject.toml because crewai hard-pins `chromadb~=1.1.0` and
# `json-repair~=0.25.2`, both carrying critical advisories with no fixed
# release on PyPI. uv.lock no longer contains either package, so there is
# nothing left to ignore here. See integrations/crewai/README.md for how to
# use the CrewAI integration with a manually installed crewai.
# ---------------------------------------------------------------------------