Thanks for contributing to ai-plugin-scanner.
This repository ships:
hol-guardfor local harness protectionplugin-scannerfor CI and maintainer checks across supported AI plugin ecosystems
- Search existing issues before opening a new report.
- Use discussions for design questions, proposals, and broader feedback.
- Open a pull request for code or documentation changes. PRs against
mainare the normal contribution path.
git clone https://github.com/hashgraph-online/ai-plugin-scanner.git
cd ai-plugin-scanner
uv sync --extra dev --extra ciscoFor lean baseline validation on Python 3.10, use uv sync --extra dev --python 3.10 instead.
If you prefer a virtualenv-first workflow, the repository can also be installed in editable mode:
python -m venv .venv
source .venv/bin/activate
pip install -e ".[dev,cisco]"The editable Cisco extra is intended for Python 3.11+ contributor environments.
All non-trivial changes should include or update automated tests.
Run the standard validation commands before opening or updating a pull request:
# If using uv:
uv run python -m ruff check src tests
uv run python -m ruff format --check src tests
uv run pytest --tb=short
# If using pip (with the virtualenv activated):
python -m ruff check src tests
python -m ruff format --check src tests
pytest --tb=shortIf you changed packaging or release logic, also verify the build:
# If using uv:
uv run python -m build
# If using pip:
python -m build- Fork the repository.
- Create a feature branch from
main. - Make the smallest coherent change that fixes the issue or adds the feature.
- Add or update tests for new functionality and changed behavior.
- Run the validation commands above.
- Open a pull request against
mainwith a clear summary of what changed and why.
- Python code should remain compatible with the versions declared in
pyproject.toml. - Keep command examples and package names aligned with the current product names:
hol-guard,plugin-scanner, andai-plugin-scanner. - Update user-facing docs when the CLI surface, GitHub Action contract, trust scoring behavior, or published workflows change.
- Do not commit secrets, credentials, or local environment files.
By contributing, you agree that your contributions will be licensed under Apache-2.0.