cfgit-impact
Optional system-impact analysis for cfgit.
This package is deliberately outside src/cfg/core/. The cfgit core stays LLM-free and provider-free; this plugin owns both deterministic impact analysis and optional LLM narration.
Install
Install cfgit with the database extras you use, then install the optional impact plugin from PyPI into the same Python environment:
pip install 'cfgit[mongo,postgres,mcp]'
pip install cfgit-impact
For pipx installs:
pipx install 'cfgit[mongo,postgres,mcp]'
pipx inject cfgit cfgit-impact
Boundary
src/cfg/core/never imports this plugin.src/cfg/core/never imports vendor SDKs or provider clients.- The main action layer imports
cfg_impact.overviewonly whencfg impactor the UI/MCP impact action is called. - Provider selection comes from
[connections].ai_providerunless a caller passesprovider.
Provider Pattern
The provider layer uses a small factory pattern:
cfg_impact.providers.base.BaseImpactProvidercfg_impact.providers.factory.ImpactProviderFactorycfg_impact.providers.claude.ClaudeProvidercfg_impact.providers.openai_provider.OpenAIProvidercfg_impact.providers.gemini.GeminiProvider
The impact engine calls narrate() or complete(). It never imports a vendor module directly.
Commands
Deterministic local analysis:
cfg impact agent_configs:agent_planner =HEAD =live --json
Opt-in LLM narration:
cfg impact agent_configs:agent_planner =HEAD =live --llm --json
Scope narration to selected records instead of the whole system:
cfg impact agent_configs:agent_planner --against agent_configs:critic --against modelgarden_models:openai/gpt-4o-mini --llm --json
LLM narration is refused unless the record is listed in
[connections].share_with_ai. The payload sent to the provider is bounded and
secret-stripped. It includes real before/after field diffs for the changed record,
plus only allowlisted text from related records. In scoped mode, only selected
records are included in the system map.
The plugin uses ANTHROPIC_API_KEY for claude, OPENAI_API_KEY for openai,
and GEMINI_API_KEY or GOOGLE_API_KEY for gemini.
Metadata
Release files for cfgit-impact 0.4.7
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| cfgit_impact-0.4.7.tar.gz | 11.2 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| cfgit_impact-0.4.7-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 25.8 kB
Release files / cfgit_impact-0.4.7.tar.gz
| Download URL | cfgit_impact-0.4.7.tar.gz |
|---|---|
| Size | 11.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
157caa288598b9bb2c039e1d0fb3997d01367cb52cfa1dc87c26fffdd1ab9b54
|
|
BLAKE2b-256 checksum How to use checksums |
3ae932493e936a83d9fdecdbd925cd079142c2169215625a39c6d5720ec96f75
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 2, 2026.
Transparency logRelease files / cfgit_impact-0.4.7-py3-none-any.whl
| Download URL | cfgit_impact-0.4.7-py3-none-any.whl |
|---|---|
| Size | 14.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
a511866e42f255dc9c6eff9c206da4b678c5de0505fee427309c6b7119b2a85f
|
|
BLAKE2b-256 checksum How to use checksums |
16845c86c02e1e113c49574cb6c01108dbbbb1b793a772019576d98d3dd1cf1c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 2, 2026.
Transparency log