Skip to content

AAK-MCP-LINEAGE-STAINLESS-001: Stainless-generator provenance / lineage (informational)

Severity
INFO
Category
Supply Chain (supply-chain)
Scanner
agent_audit_kit/scanners/stainless_lineage.py
Auto-fixable
No.
SARIF name
StainlessLineageProvenance

What it detects

The source tree contains a Stainless auto-generation marker — either the in-file banner File generated from our OpenAPI spec by Stainless. (verified verbatim against github.com/anthropics/anthropic-sdk-python on 2026-05-19) or a stainless.yml / .stainless/ config-as-code shape at the project root. Stainless is the API-spec-to-SDK / CLI / MCP-server generator Anthropic acquired on 2026-05-18. This rule is provenance, not vulnerability — severity INFO. It surfaces the generator lineage so procurement teams and SBOM tooling can answer 'which of our MCP servers / SDKs are generator-produced vs hand-authored.' The Anthropic announcement makes no mention of winding down the generator or of pre-vs-post-acquisition default differences; AAK does not fabricate either claim. If a future CVE class lands against a specific Stainless generator version, this rule will be re-targeted to fire only on the affected lineage.

How to fix

No action required for the rule fire itself — this is a lineage data point. For SBOM / supply-chain attestation, record the Stainless lineage alongside the package's own version metadata. INFO findings are not shown by default, since aak scan reports from low up; aak scan --severity info shows them. To suppress the rule even then, list its id under exclude-rules in .agent-audit-kit.yml, or run aak scan --exclude-rules AAK-MCP-LINEAGE-STAINLESS-001.

To confirm the finding is gone, report only this rule:

agent-audit-kit scan . --rules AAK-MCP-LINEAGE-STAINLESS-001

Limitations

Looks for the banner File generated from our OpenAPI spec by Stainless or Code generated by Stainless in the first 8 lines of .py, .ts, .tsx, .js, .mjs, .cjs, .go, .java, .kt, .rb, .cs and .php files outside .git, node_modules, dist, build, .venv, venv and __pycache__, and for a stainless.yml-style config file or a .stainless/ directory at the project root. A banner below line 8 (under a long licence header), a generated SDK installed as a dependency under node_modules, and a config file in a sub-directory are not reported.

References


All rules. This page is generated from the rule registry when the documentation is built; to change it, change the rule in agent_audit_kit/rules/builtin.py. To give the rule a hand-written write-up, add docs/rules/AAK-MCP-LINEAGE-STAINLESS-001.md: the page then shows that text, with the registry reference appended under it.