agentsec-cli 0.1.0__tar.gz → 1.0.1__tar.gz

agentsec_cli-1.0.1/CHANGELOG.md

@@ -0,0 +1,30 @@
+# CHANGELOG
+
+All notable changes to AgentSec will be documented in this file.
+
+The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
+and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
+
+## [1.0.0] - 2026-07-02
+
+### Added
+
+- Initial public release.
+- 41 security rules for MCP, Cursor, Claude Desktop, Codex, Cline, and Continue configurations.
+- CLI interface with `scan` command.
+- Output formats: terminal, JSON, SARIF, Markdown.
+- OWASP Top 10 for LLM Applications (LLM01–LLM10) mapping on every rule.
+- OWASP Agentic Security Top 10 (AG01–AG10) mapping on applicable rules.
+- CI/CD gating with `--fail-on critical|high|medium|low`.
+- Baseline/lockfile support with `--baseline` and `--update-baseline`.
+- SARIF v2.1.0 output for GitHub CodeQL integration.
+- Support for JSON, YAML, TOML, Markdown config files.
+- Automatic detection of MCP server manifests, Claude Desktop configs, Cursor rules, Codex configs, Cline configs, and agent instruction files.
+- MkDocs documentation (installation, usage, rules reference, OWASP mapping, FAQ, CI/CD).
+- Landing page at https://locface.github.io/AgentSec/.
+- PyPI package `agentsec-cli`.
+
+### Security
+
+- Every security rule is mapped to industry-standard OWASP frameworks.
+- No LLM dependencies — purely static analysis, zero data leakage.

agentsec_cli-1.0.1/CODE_OF_CONDUCT.md

@@ -0,0 +1,133 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our
+community a harassment-free experience for everyone, regardless of age, body
+size, visible or invisible disability, ethnicity, sex characteristics, gender
+identity and expression, level of experience, education, socio-economic status,
+nationality, personal appearance, race, caste, color, religion, or sexual
+identity and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming,
+diverse, inclusive, and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment for our
+community include:
+
+* Demonstrating empathy and kindness toward other people
+* Being respectful of differing opinions, viewpoints, and experiences
+* Giving and gracefully accepting constructive feedback
+* Accepting responsibility and apologizing to those affected by our mistakes,
+  and learning from the experience
+* Focusing on what is best not just for us as individuals, but for the overall
+  community
+
+Examples of unacceptable behavior include:
+
+* The use of sexualized language or imagery, and sexual attention or advances of
+  any kind
+* Trolling, insulting or derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or email address,
+  without their explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Enforcement Responsibilities
+
+Community leaders are responsible for clarifying and enforcing our standards of
+acceptable behavior and will take appropriate and fair corrective action in
+response to any behavior that they deem inappropriate, threatening, offensive,
+or harmful.
+
+Community leaders have the right and responsibility to remove, edit, or reject
+comments, commits, code, wiki edits, issues, and other contributions that are
+not aligned to this Code of Conduct, and will communicate reasons for moderation
+decisions when appropriate.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when
+an individual is officially representing the community in public spaces.
+Examples of representing our community include using an official email address,
+posting via an official social media account, or acting as an appointed
+representative at an online or offline event.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported to the community leaders responsible for enforcement at
+locface (via GitHub Issues).
+
+All complaints will be reviewed and investigated promptly and fairly.
+
+All community leaders are obligated to respect the privacy and security of the
+reporter of any incident.
+
+## Enforcement Guidelines
+
+Community leaders will follow these Community Impact Guidelines in determining
+the consequences for any action they deem in violation of this Code of Conduct:
+
+### 1. Correction
+
+**Community Impact**: Use of inappropriate language or other behavior deemed
+unprofessional or unwelcome in the community.
+
+**Consequence**: A private, written warning from community leaders, providing
+clarity around the nature of the violation and an explanation of why the
+behavior was inappropriate. A public apology may be requested.
+
+### 2. Warning
+
+**Community Impact**: A violation through a single incident or series of
+actions.
+
+**Consequence**: A warning with consequences for continued behavior. No
+interaction with the people involved, including unsolicited interaction with
+those enforcing the Code of Conduct, for a specified period of time. This
+includes avoiding interactions in community spaces as well as external channels
+like social media. Violating these terms may lead to a temporary or permanent
+ban.
+
+### 3. Temporary Ban
+
+**Community Impact**: A serious violation of community standards, including
+sustained inappropriate behavior.
+
+**Consequence**: A temporary ban from any sort of interaction or public
+communication with the community for a specified period of time. No public or
+private interaction with the people involved, including unsolicited interaction
+with those enforcing the Code of Conduct, is allowed during this period.
+Violating these terms may lead to a permanent ban.
+
+### 4. Permanent Ban
+
+**Community Impact**: Demonstrating a pattern of violation of community
+standards, including sustained inappropriate behavior, harassment of an
+individual, or aggression toward or disparagement of classes of individuals.
+
+**Consequence**: A permanent ban from any sort of public interaction within the
+community.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage],
+version 2.1, available at
+[https://www.contributor-covenant.org/version/2/1/code_of_conduct.html][v2.1].
+
+Community Impact Guidelines were inspired by
+[Mozilla's code of conduct enforcement ladder][Mozilla CoC].
+
+For answers to common questions about this code of conduct, see the FAQ at
+[https://www.contributor-covenant.org/faq][FAQ]. Translations are available at
+[https://www.contributor-covenant.org/translations][translations].
+
+[homepage]: https://www.contributor-covenant.org
+[v2.1]: https://www.contributor-covenant.org/version/2/1/code_of_conduct.html
+[Mozilla CoC]: https://github.com/mozilla/diversity
+[FAQ]: https://www.contributor-covenant.org/faq
+[translations]: https://www.contributor-covenant.org/translations

agentsec_cli-1.0.1/CONTRIBUTING.md

@@ -0,0 +1,177 @@
+# Contributing to AgentSec
+
+Thank you for considering contributing to AgentSec. This document outlines the process for contributing code, reporting issues, and improving documentation.
+
+## Table of Contents
+
+- [Development Setup](#development-setup)
+- [Running Tests](#running-tests)
+- [Code Style](#code-style)
+- [Commit Style](#commit-style)
+- [Branch Naming](#branch-naming)
+- [Pull Request Workflow](#pull-request-workflow)
+- [Reporting Issues](#reporting-issues)
+- [Review Process](#review-process)
+
+## Development Setup
+
+### Prerequisites
+
+- Python 3.10 or later
+- git
+
+### Setup
+
+```bash
+# Clone the repository
+git clone https://github.com/locface/AgentSec.git
+cd AgentSec
+
+# Create a virtual environment
+python3 -m venv .venv
+source .venv/bin/activate
+
+# Install in development mode
+pip install -e .[dev]
+
+# Verify installation
+agentsec --help
+```
+
+## Running Tests
+
+```bash
+# Run all tests
+pytest
+
+# Run with verbose output
+pytest -v
+
+# Run a specific test file
+pytest tests/test_baseline.py
+
+# Run tests with coverage
+pip install pytest-cov
+pytest --cov=agentsec
+```
+
+Tests are located in the `tests/` directory. Each test file follows the `test_*.py` naming convention.
+
+### Writing Tests
+
+- Place test files in `tests/`
+- Name test files `test_<module>.py`
+- Use descriptive test function names
+- Use fixtures for sample configs (see `tests/fixtures/`)
+- Test each rule independently
+- Prefer behavioral assertions over snapshot comparisons
+
+## Code Style
+
+- Follow [PEP 8](https://peps.python.org/pep-0008/) for Python code.
+- Use type hints for all function signatures.
+- Maximum line length: 100 characters.
+- Use descriptive variable names — avoid single-letter names except in comprehensions.
+- Prefer `pathlib.Path` over `os.path`.
+- Use `pathlib.Path` for file operations.
+- Keep functions focused and small.
+
+## Commit Style
+
+We follow [Conventional Commits](https://www.conventionalcommits.org/):
+
+```
+<type>: <description>
+
+[optional body]
+```
+
+Types:
+
+- `feat:` — new feature
+- `fix:` — bug fix
+- `docs:` — documentation only
+- `style:` — formatting, missing semicolons, etc.
+- `refactor:` — code change that neither fixes a bug nor adds a feature
+- `test:` — adding or modifying tests
+- `chore:` — build process, dependencies, etc.
+- `perf:` — performance improvement
+- `ci:` — CI configuration
+- `security:` — security fixes
+
+Examples:
+
+```
+feat: add --fail-on flag for CI gating
+fix: handle missing server field in json output
+docs: add SARIF integration example
+```
+
+## Branch Naming
+
+- `feat/<short-description>` — new features
+- `fix/<short-description>` — bug fixes
+- `docs/<short-description>` — documentation
+- `chore/<short-description>` — maintenance
+
+Use hyphens to separate words. Keep names short but descriptive.
+
+## Pull Request Workflow
+
+1. Fork the repository.
+2. Create a branch from `main`.
+3. Make your changes.
+4. Run tests: `pytest`.
+5. Ensure your code follows the style guide.
+6. Commit using conventional commit format.
+7. Push your branch and open a pull request.
+8. In the PR description, explain what the change does and why.
+9. Ensure CI passes.
+10. Request review from a maintainer.
+
+### Pull Request Checklist
+
+- [ ] Tests pass (`pytest`)
+- [ ] New tests added for new functionality
+- [ ] Code follows project style
+- [ ] Documentation updated (if applicable)
+- [ ] CHANGELOG entry added (if applicable)
+- [ ] Commits follow conventional commit format
+- [ ] Branch is up-to-date with `main`
+
+## Reporting Issues
+
+### Bug Reports
+
+When filing a bug report, include:
+
+- AgentSec version (`agentsec --version` or `pip show agentsec-cli`)
+- Python version
+- Operating system
+- Steps to reproduce
+- Expected behavior
+- Actual behavior
+- Sample input (if possible, sanitize sensitive data)
+
+### Feature Requests
+
+When requesting a feature, describe:
+
+- What you want to do
+- Why existing functionality doesn't cover it
+- How you envision the feature working (API, flags, etc.)
+
+### Security Issues
+
+For security vulnerabilities, **do not** file a public issue. Instead, follow the process in [SECURITY.md](./SECURITY.md).
+
+## Review Process
+
+1. A maintainer will review your PR within a few days.
+2. Address any feedback with additional commits.
+3. Once approved, a maintainer will merge your PR.
+4. The change will be included in the next release.
+
+## Questions?
+
+If you have questions, open a [Discussion](https://github.com/locface/AgentSec/discussions) or reach out via the issue tracker.

agentsec_cli-1.0.1/MANIFEST.in

@@ -0,0 +1,8 @@
+include README.md
+include LICENSE
+include CHANGELOG.md
+include SECURITY.md
+include CONTRIBUTING.md
+include CODE_OF_CONDUCT.md
+include pyproject.toml
+recursive-include agentsec *.py

agentsec_cli-1.0.1/PKG-INFO

@@ -0,0 +1,137 @@
+Metadata-Version: 2.4
+Name: agentsec-cli
+Version: 1.0.1
+Summary: Static security scanner for AI coding agents and MCP configurations
+Author: locface
+License-Expression: MIT
+Project-URL: homepage, https://locface.github.io/AgentSec/
+Project-URL: repository, https://github.com/locface/AgentSec
+Project-URL: documentation, https://locface.github.io/AgentSec/docs/
+Project-URL: changelog, https://github.com/locface/AgentSec/blob/main/CHANGELOG.md
+Classifier: Development Status :: 5 - Production/Stable
+Classifier: Intended Audience :: Developers
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.10
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Requires-Python: >=3.10
+Description-Content-Type: text/markdown
+License-File: LICENSE
+Requires-Dist: click<9,>=8.0.0
+Requires-Dist: pyyaml<7,>=6.0
+Requires-Dist: toml<1,>=0.10.2
+Requires-Dist: tomli<3,>=2.0.1; python_version < "3.11"
+Provides-Extra: dev
+Requires-Dist: pytest>=7.0.0; extra == "dev"
+Dynamic: license-file
+
+<picture>
+  <source media="(prefers-color-scheme: dark)" srcset="https://raw.githubusercontent.com/locface/AgentSec/main/docs/images/agentsec-dark.svg">
+  <img alt="AgentSec" src="https://raw.githubusercontent.com/locface/AgentSec/main/docs/images/agentsec-light.svg">
+</picture>
+
+# AgentSec
+
+**Static security scanner for AI coding agents and MCP configurations.**
+
+[![PyPI](https://img.shields.io/pypi/v/agentsec-cli.svg)](https://pypi.org/project/agentsec-cli/)
+[![Python](https://img.shields.io/pypi/pyversions/agentsec-cli.svg)](https://pypi.org/project/agentsec-cli/)
+[![License](https://img.shields.io/github/license/locface/AgentSec)](LICENSE)
+[![Tests](https://img.shields.io/github/actions/workflow/status/locface/AgentSec/agentsec.yml?label=tests)](https://github.com/locface/AgentSec/actions)
+
+AI coding agents have access to your shell, filesystem, network, and secrets. Most agent configurations are never audited for security risks. AgentSec inspects MCP server manifests, Claude Desktop configs, Cursor rules, and agent instruction files for dangerous permissions, prompt injection risks, and secret exposure — with no LLM dependencies and no data leaving your machine.
+
+All findings map to [OWASP Top 10 for LLM Applications](https://genai.owasp.org/) (LLM01–LLM10) and the [OWASP Agentic Security Top 10](https://owasp.org/) (AG01–AG10).
+
+## Features
+
+- 41 security rules covering shell execution, filesystem access, network exfiltration, OAuth scopes, prompt injection, container escape, and credential exposure
+- OWASP LLM + Agentic mapping on every finding
+- 4 output formats: terminal, JSON, Markdown, SARIF v2.1.0
+- CI/CD gating with `--fail-on` (exit code 1 at severity threshold)
+- Baseline comparison for regression tracking
+- Automatic detection of JSON, YAML, TOML, and Markdown configs
+- Zero runtime dependencies beyond the Python standard library
+
+## Installation
+
+```bash
+pip install agentsec-cli
+```
+
+Requires Python 3.10 or later.
+
+## Quick Start
+
+```bash
+# Scan a project
+agentsec scan /path/to/project
+
+# Generate SARIF for CI/CD
+agentsec scan . --format sarif > results.sarif
+
+# Gate CI on critical findings
+agentsec scan . --fail-on critical
+
+# Baseline comparison
+agentsec scan . --update-baseline baseline.json
+agentsec scan . --baseline baseline.json
+
+# OWASP mapping
+agentsec scan . --show-owasp
+```
+
+Example output:
+
+```text
+ Scanning /home/user/dev/mcp-project...
+
+[CRITICAL] MCP shell execution
+  File: claude_desktop_config.json
+  Server: shell-server
+  Description: MCP server can execute shell commands
+  Recommendation: Require explicit approval or remove shell access.
+
+[CRITICAL] MCP filesystem write access
+  File: claude_desktop_config.json
+  Server: filesystem
+  Description: MCP server has filesystem write access
+  Recommendation: Restrict filesystem access to read-only or specific directories.
+
+Total findings: 4 · Critical: 3 · High: 0 · Medium: 1 · Low: 0
+```
+
+### Output Formats
+
+- **terminal** (default) — human-readable with severity coloring
+- **json** — machine-parseable JSON array of findings
+- **markdown** — formatted report suitable for commit comments
+- **sarif** — SARIF v2.1.0, compatible with GitHub CodeQL
+
+### Supported Config Files
+
+AgentSec automatically detects and scans these file types:
+
+- MCP servers: `mcp.json`, `mcp.yaml`, `mcp.toml`
+- Claude Desktop: `claude_desktop_config.json`
+- Cursor: `.cursorrules`, `.cursor/rules/*`
+- Codex / Cline: `codex.toml`, `.clinerules`
+- Agent instructions: `AGENTS.md`, `CLAUDE.md`
+- Infrastructure: `Dockerfile`, `package.json`
+
+## Documentation
+
+Full documentation: [https://locface.github.io/AgentSec/docs/](https://locface.github.io/AgentSec/docs/)
+
+## Contributing
+
+See [CONTRIBUTING.md](CONTRIBUTING.md) for development setup, testing, and pull request workflow.
+
+## Security
+
+Report vulnerabilities privately. See [SECURITY.md](SECURITY.md) for our disclosure policy.
+
+## License
+
+MIT — see [LICENSE](LICENSE).

agentsec_cli-1.0.1/README.md

@@ -0,0 +1,109 @@
+<picture>
+  <source media="(prefers-color-scheme: dark)" srcset="https://raw.githubusercontent.com/locface/AgentSec/main/docs/images/agentsec-dark.svg">
+  <img alt="AgentSec" src="https://raw.githubusercontent.com/locface/AgentSec/main/docs/images/agentsec-light.svg">
+</picture>
+
+# AgentSec
+
+**Static security scanner for AI coding agents and MCP configurations.**
+
+[![PyPI](https://img.shields.io/pypi/v/agentsec-cli.svg)](https://pypi.org/project/agentsec-cli/)
+[![Python](https://img.shields.io/pypi/pyversions/agentsec-cli.svg)](https://pypi.org/project/agentsec-cli/)
+[![License](https://img.shields.io/github/license/locface/AgentSec)](LICENSE)
+[![Tests](https://img.shields.io/github/actions/workflow/status/locface/AgentSec/agentsec.yml?label=tests)](https://github.com/locface/AgentSec/actions)
+
+AI coding agents have access to your shell, filesystem, network, and secrets. Most agent configurations are never audited for security risks. AgentSec inspects MCP server manifests, Claude Desktop configs, Cursor rules, and agent instruction files for dangerous permissions, prompt injection risks, and secret exposure — with no LLM dependencies and no data leaving your machine.
+
+All findings map to [OWASP Top 10 for LLM Applications](https://genai.owasp.org/) (LLM01–LLM10) and the [OWASP Agentic Security Top 10](https://owasp.org/) (AG01–AG10).
+
+## Features
+
+- 41 security rules covering shell execution, filesystem access, network exfiltration, OAuth scopes, prompt injection, container escape, and credential exposure
+- OWASP LLM + Agentic mapping on every finding
+- 4 output formats: terminal, JSON, Markdown, SARIF v2.1.0
+- CI/CD gating with `--fail-on` (exit code 1 at severity threshold)
+- Baseline comparison for regression tracking
+- Automatic detection of JSON, YAML, TOML, and Markdown configs
+- Zero runtime dependencies beyond the Python standard library
+
+## Installation
+
+```bash
+pip install agentsec-cli
+```
+
+Requires Python 3.10 or later.
+
+## Quick Start
+
+```bash
+# Scan a project
+agentsec scan /path/to/project
+
+# Generate SARIF for CI/CD
+agentsec scan . --format sarif > results.sarif
+
+# Gate CI on critical findings
+agentsec scan . --fail-on critical
+
+# Baseline comparison
+agentsec scan . --update-baseline baseline.json
+agentsec scan . --baseline baseline.json
+
+# OWASP mapping
+agentsec scan . --show-owasp
+```
+
+Example output:
+
+```text
+ Scanning /home/user/dev/mcp-project...
+
+[CRITICAL] MCP shell execution
+  File: claude_desktop_config.json
+  Server: shell-server
+  Description: MCP server can execute shell commands
+  Recommendation: Require explicit approval or remove shell access.
+
+[CRITICAL] MCP filesystem write access
+  File: claude_desktop_config.json
+  Server: filesystem
+  Description: MCP server has filesystem write access
+  Recommendation: Restrict filesystem access to read-only or specific directories.
+
+Total findings: 4 · Critical: 3 · High: 0 · Medium: 1 · Low: 0
+```
+
+### Output Formats
+
+- **terminal** (default) — human-readable with severity coloring
+- **json** — machine-parseable JSON array of findings
+- **markdown** — formatted report suitable for commit comments
+- **sarif** — SARIF v2.1.0, compatible with GitHub CodeQL
+
+### Supported Config Files
+
+AgentSec automatically detects and scans these file types:
+
+- MCP servers: `mcp.json`, `mcp.yaml`, `mcp.toml`
+- Claude Desktop: `claude_desktop_config.json`
+- Cursor: `.cursorrules`, `.cursor/rules/*`
+- Codex / Cline: `codex.toml`, `.clinerules`
+- Agent instructions: `AGENTS.md`, `CLAUDE.md`
+- Infrastructure: `Dockerfile`, `package.json`
+
+## Documentation
+
+Full documentation: [https://locface.github.io/AgentSec/docs/](https://locface.github.io/AgentSec/docs/)
+
+## Contributing
+
+See [CONTRIBUTING.md](CONTRIBUTING.md) for development setup, testing, and pull request workflow.
+
+## Security
+
+Report vulnerabilities privately. See [SECURITY.md](SECURITY.md) for our disclosure policy.
+
+## License
+
+MIT — see [LICENSE](LICENSE).

agentsec_cli-1.0.1/SECURITY.md

@@ -0,0 +1,65 @@
+# Security Policy
+
+## Supported Versions
+
+| Version | Supported          |
+|---------|--------------------|
+| 1.0.x   | :white_check_mark: |
+| < 1.0   | :x:                |
+
+## Reporting a Vulnerability
+
+AgentSec takes security vulnerabilities seriously. We appreciate your efforts to responsibly disclose your findings.
+
+### How to Report
+
+Please **do not** file a public issue for security vulnerabilities. Instead, send a private report via one of the following methods:
+
+1. **GitHub Private Vulnerability Reporting**: Use the "Report a vulnerability" feature under the repository's Security tab.
+2. **Email**: Send details to the maintainer via locface@users.noreply.github.com.
+
+### What to Include
+
+- Type of issue (e.g., code execution, data exposure, etc.)
+- Full paths of source file(s) related to the manifestation of the issue
+- The location of the affected source code (tag/branch/commit or direct URL)
+- Any special configuration required to reproduce the issue
+- Step-by-step instructions to reproduce the issue
+- Proof-of-concept or exploit code (if possible)
+- Impact of the issue, including how an attacker might exploit it
+
+### Response Expectations
+
+- **Acknowledgement**: We will acknowledge receipt of your report within 48 hours.
+- **Status Update**: We will provide a status update within 5 business days.
+- **Fix Timeline**: We aim to release a fix within 14 days for critical issues, depending on complexity.
+- **Disclosure**: We will coordinate disclosure timing with you.
+
+## Disclosure Policy
+
+- We request that you give us 90 days from the time you report the issue to release a fix before publishing details.
+- We will publish a security advisory on GitHub once the fix is released.
+- We will credit the reporter in the advisory unless they request anonymity.
+
+## Scope
+
+The following are in scope:
+
+- The `agentsec` Python package (source code in this repository)
+- Documentation generation and CI/CD integrations
+
+The following are out of scope:
+
+- Third-party MCP servers used as example data
+- The landing page website (report separately via the landing page repository)
+- Previously reported issues that have been fixed
+
+## Safe Harbor
+
+We consider security research conducted under this policy to be:
+
+- Authorized conduct under the Computer Fraud and Abuse Act
+- Exempt from any anti-circumvention provisions in our Terms of Service
+- Lawful, and we will not pursue legal action against researchers acting in good faith
+
+Please act in good faith — do not intentionally damage systems or access data beyond what is necessary to demonstrate the vulnerability.

{agentsec_cli-0.1.0 → agentsec_cli-1.0.1}/agentsec/__init__.py

@@ -1,3 +1,3 @@
 """AgentSec: Static security scanner for AI coding agents and MCP configs."""
 
-__version__ = "0.1.0"
+__version__ = "1.0.1"