coding-agent-audit 0.3.1__tar.gz → 0.3.2__tar.gz

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (22) hide show
  1. {coding_agent_audit-0.3.1/src/coding_agent_audit.egg-info → coding_agent_audit-0.3.2}/PKG-INFO +4 -3
  2. {coding_agent_audit-0.3.1 → coding_agent_audit-0.3.2}/README.md +3 -2
  3. {coding_agent_audit-0.3.1 → coding_agent_audit-0.3.2}/pyproject.toml +2 -1
  4. {coding_agent_audit-0.3.1 → coding_agent_audit-0.3.2}/src/agentaudit/__init__.py +1 -1
  5. {coding_agent_audit-0.3.1 → coding_agent_audit-0.3.2/src/coding_agent_audit.egg-info}/PKG-INFO +4 -3
  6. {coding_agent_audit-0.3.1 → coding_agent_audit-0.3.2}/src/coding_agent_audit.egg-info/entry_points.txt +1 -0
  7. {coding_agent_audit-0.3.1 → coding_agent_audit-0.3.2}/LICENSE +0 -0
  8. {coding_agent_audit-0.3.1 → coding_agent_audit-0.3.2}/setup.cfg +0 -0
  9. {coding_agent_audit-0.3.1 → coding_agent_audit-0.3.2}/src/agentaudit/checks.py +0 -0
  10. {coding_agent_audit-0.3.1 → coding_agent_audit-0.3.2}/src/agentaudit/cli.py +0 -0
  11. {coding_agent_audit-0.3.1 → coding_agent_audit-0.3.2}/src/agentaudit/configscan.py +0 -0
  12. {coding_agent_audit-0.3.1 → coding_agent_audit-0.3.2}/src/agentaudit/findings.py +0 -0
  13. {coding_agent_audit-0.3.1 → coding_agent_audit-0.3.2}/src/agentaudit/iocs.py +0 -0
  14. {coding_agent_audit-0.3.1 → coding_agent_audit-0.3.2}/src/agentaudit/mcp_server.py +0 -0
  15. {coding_agent_audit-0.3.1 → coding_agent_audit-0.3.2}/src/coding_agent_audit.egg-info/SOURCES.txt +0 -0
  16. {coding_agent_audit-0.3.1 → coding_agent_audit-0.3.2}/src/coding_agent_audit.egg-info/dependency_links.txt +0 -0
  17. {coding_agent_audit-0.3.1 → coding_agent_audit-0.3.2}/src/coding_agent_audit.egg-info/requires.txt +0 -0
  18. {coding_agent_audit-0.3.1 → coding_agent_audit-0.3.2}/src/coding_agent_audit.egg-info/top_level.txt +0 -0
  19. {coding_agent_audit-0.3.1 → coding_agent_audit-0.3.2}/tests/test_checks.py +0 -0
  20. {coding_agent_audit-0.3.1 → coding_agent_audit-0.3.2}/tests/test_cli.py +0 -0
  21. {coding_agent_audit-0.3.1 → coding_agent_audit-0.3.2}/tests/test_configscan.py +0 -0
  22. {coding_agent_audit-0.3.1 → coding_agent_audit-0.3.2}/tests/test_mcp_server.py +0 -0
{coding_agent_audit-0.3.1/src/coding_agent_audit.egg-info → coding_agent_audit-0.3.2}/PKG-INFO RENAMED
@@ -1,6 +1,6 @@
1
1
  Metadata-Version: 2.4
2
2
  Name: coding-agent-audit
3
- Version: 0.3.1
3
+ Version: 0.3.2
4
4
  Summary: Scan your machine for known AI-coding-assistant supply-chain backdoor indicators (Claude Code / Cursor / Windsurf extensions, MCP servers) plus risky hook/permission config patterns. Usable as a CLI or as an MCP server.
5
5
  Author-email: StackScribe AI <survivalagent320@gmail.com>
6
6
  License: MIT
@@ -133,14 +133,15 @@ any MCP client. Add this to your client's MCP config (e.g. Claude Desktop's
133
133
  "mcpServers": {
134
134
  "coding-agent-audit": {
135
135
  "command": "uvx",
136
- "args": ["--from", "coding-agent-audit", "agent-audit-mcp"]
136
+ "args": ["coding-agent-audit"]
137
137
  }
138
138
  }
139
139
  }
140
140
  ```
141
141
 
142
142
  (No `uv`? `pip install coding-agent-audit` then use `"command": "agent-audit-mcp"`
143
- with no `args`.) This exposes two tools, `scan_for_known_backdoors` and
143
+ with no `args` — same server, explicit entry-point name.) This exposes two
144
+ tools, `scan_for_known_backdoors` and
144
145
  `scan_mcp_config`, so you can just ask your assistant "scan my machine for
145
146
  AI coding assistant backdoors" and read the result in the chat — same
146
147
  heuristics as the CLI above, nothing installed beyond the server itself.
{coding_agent_audit-0.3.1 → coding_agent_audit-0.3.2}/README.md RENAMED
@@ -112,14 +112,15 @@ any MCP client. Add this to your client's MCP config (e.g. Claude Desktop's
112
112
  "mcpServers": {
113
113
  "coding-agent-audit": {
114
114
  "command": "uvx",
115
- "args": ["--from", "coding-agent-audit", "agent-audit-mcp"]
115
+ "args": ["coding-agent-audit"]
116
116
  }
117
117
  }
118
118
  }
119
119
  ```
120
120
 
121
121
  (No `uv`? `pip install coding-agent-audit` then use `"command": "agent-audit-mcp"`
122
- with no `args`.) This exposes two tools, `scan_for_known_backdoors` and
122
+ with no `args` — same server, explicit entry-point name.) This exposes two
123
+ tools, `scan_for_known_backdoors` and
123
124
  `scan_mcp_config`, so you can just ask your assistant "scan my machine for
124
125
  AI coding assistant backdoors" and read the result in the chat — same
125
126
  heuristics as the CLI above, nothing installed beyond the server itself.
{coding_agent_audit-0.3.1 → coding_agent_audit-0.3.2}/pyproject.toml RENAMED
@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
4
4
 
5
5
  [project]
6
6
  name = "coding-agent-audit"
7
- version = "0.3.1"
7
+ version = "0.3.2"
8
8
  description = "Scan your machine for known AI-coding-assistant supply-chain backdoor indicators (Claude Code / Cursor / Windsurf extensions, MCP servers) plus risky hook/permission config patterns. Usable as a CLI or as an MCP server."
9
9
  readme = "README.md"
10
10
  requires-python = ">=3.9"
@@ -30,6 +30,7 @@ Homepage = "https://github.com/stackscribe-ai/coding-agent-audit"
30
30
  [project.scripts]
31
31
  agent-audit = "agentaudit.cli:main"
32
32
  agent-audit-mcp = "agentaudit.mcp_server:main"
33
+ coding-agent-audit = "agentaudit.mcp_server:main"
33
34
 
34
35
  [tool.setuptools.packages.find]
35
36
  where = ["src"]
{coding_agent_audit-0.3.1 → coding_agent_audit-0.3.2}/src/agentaudit/__init__.py RENAMED
@@ -3,4 +3,4 @@ for AI coding assistants (Claude Code, Cursor, Windsurf, VS Code forks, MCP
3
3
  servers).
4
4
  """
5
5
 
6
- __version__ = "0.3.1"
6
+ __version__ = "0.3.2"
{coding_agent_audit-0.3.1 → coding_agent_audit-0.3.2/src/coding_agent_audit.egg-info}/PKG-INFO RENAMED
@@ -1,6 +1,6 @@
1
1
  Metadata-Version: 2.4
2
2
  Name: coding-agent-audit
3
- Version: 0.3.1
3
+ Version: 0.3.2
4
4
  Summary: Scan your machine for known AI-coding-assistant supply-chain backdoor indicators (Claude Code / Cursor / Windsurf extensions, MCP servers) plus risky hook/permission config patterns. Usable as a CLI or as an MCP server.
5
5
  Author-email: StackScribe AI <survivalagent320@gmail.com>
6
6
  License: MIT
@@ -133,14 +133,15 @@ any MCP client. Add this to your client's MCP config (e.g. Claude Desktop's
133
133
  "mcpServers": {
134
134
  "coding-agent-audit": {
135
135
  "command": "uvx",
136
- "args": ["--from", "coding-agent-audit", "agent-audit-mcp"]
136
+ "args": ["coding-agent-audit"]
137
137
  }
138
138
  }
139
139
  }
140
140
  ```
141
141
 
142
142
  (No `uv`? `pip install coding-agent-audit` then use `"command": "agent-audit-mcp"`
143
- with no `args`.) This exposes two tools, `scan_for_known_backdoors` and
143
+ with no `args` — same server, explicit entry-point name.) This exposes two
144
+ tools, `scan_for_known_backdoors` and
144
145
  `scan_mcp_config`, so you can just ask your assistant "scan my machine for
145
146
  AI coding assistant backdoors" and read the result in the chat — same
146
147
  heuristics as the CLI above, nothing installed beyond the server itself.
{coding_agent_audit-0.3.1 → coding_agent_audit-0.3.2}/src/coding_agent_audit.egg-info/entry_points.txt RENAMED
@@ -1,3 +1,4 @@
1
1
  [console_scripts]
2
2
  agent-audit = agentaudit.cli:main
3
3
  agent-audit-mcp = agentaudit.mcp_server:main
4
+ coding-agent-audit = agentaudit.mcp_server:main