scip-cli 2.2.1__tar.gz → 2.4.0__tar.gz

{scip_cli-2.2.1 → scip_cli-2.4.0}/.cursor/rules/agent.mdc

@@ -33,8 +33,9 @@ Node.js + `npx` required for integration tests (`scip-typescript`). Optional: `S
 | Full suite | `pytest` |
 | E2e loop | `pytest tests/test_e2e.py tests/test_e2e_analyze_patterns.py` |
 | Lint / format | `ruff check .` / `ruff format .` |
+| Typecheck | `basedpyright scip_cli/` |
 
-Pre-commit: ruff + ruff-format + full pytest. E2e before commit on command changes.
+Pre-commit: ruff + ruff-format + basedpyright + full pytest. E2e before commit on command changes.
 
 ## Improving this repo (do this before review subagents)
 

scip_cli-2.4.0/.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,36 @@
+---
+name: Bug Report
+about: Report a bug or unexpected behavior
+title: '[BUG] '
+labels: bug
+assignees: ''
+---
+
+**Describe the bug**
+A clear and concise description of what the bug is.
+
+**To Reproduce**
+Steps to reproduce the behavior:
+1. Run command: `scip-cli ...`
+2. On project: [describe project type, size, language]
+3. See error
+
+**Expected behavior**
+A clear and concise description of what you expected to happen.
+
+**Actual behavior**
+What actually happened. Include error messages, stack traces, or unexpected output.
+
+**Environment**
+- OS: [e.g., Ubuntu 22.04, macOS 14.0]
+- Python version: [e.g., 3.11.5]
+- scip-cli version: [e.g., 0.5.0]
+- Node.js version: [e.g., 20.10.0] (if applicable)
+
+**Additional context**
+Add any other context about the problem here (logs, screenshots, project structure).
+
+**Checklist**
+- [ ] I've searched existing issues for similar bugs
+- [ ] I've included a minimal reproducible example (if possible)
+- [ ] I've provided my environment details

scip_cli-2.4.0/.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,33 @@
+---
+name: Feature Request
+about: Suggest an idea or enhancement
+title: '[FEATURE] '
+labels: enhancement
+assignees: ''
+---
+
+**Is your feature request related to a problem? Please describe.**
+A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
+
+**Describe the solution you'd like**
+A clear and concise description of what you want to happen.
+
+**Describe alternatives you've considered**
+A clear and concise description of any alternative solutions or features you've considered.
+
+**Use case**
+Describe your use case and how this feature would help you.
+
+**Example usage**
+If applicable, show how you'd use this feature:
+
+```bash
+scip-cli <command> [arguments]
+```
+
+**Additional context**
+Add any other context, mockups, or examples about the feature request here.
+
+**Checklist**
+- [ ] I've searched existing issues for similar feature requests
+- [ ] I've explained my use case clearly

scip_cli-2.4.0/.github/ISSUE_TEMPLATE/question.md

@@ -0,0 +1,21 @@
+---
+name: Question
+about: Ask a question about usage or behavior
+title: '[QUESTION] '
+labels: question
+assignees: ''
+---
+
+**Your question**
+A clear and concise question about scip-cli usage, behavior, or configuration.
+
+**Context**
+What are you trying to accomplish? What have you tried so far?
+
+**Environment** (if relevant)
+- OS: [e.g., Ubuntu 22.04]
+- Python version: [e.g., 3.11.5]
+- scip-cli version: [e.g., 0.5.0]
+
+**Additional context**
+Any other context, code examples, or screenshots that might help answer your question.

scip_cli-2.4.0/.github/pull_request_template.md

@@ -0,0 +1,43 @@
+## Description
+
+Brief description of what this PR does and why.
+
+Fixes #(issue)
+
+## Type of Change
+
+- [ ] Bug fix (non-breaking change that fixes an issue)
+- [ ] New feature (non-breaking change that adds functionality)
+- [ ] Breaking change (fix or feature that would cause existing functionality to change)
+- [ ] Documentation update
+- [ ] Performance improvement
+- [ ] Refactoring (no functional changes)
+
+## Changes Made
+
+- 
+- 
+- 
+
+## Testing
+
+- [ ] `pytest` passes
+- [ ] `ruff check .` passes
+- [ ] `ruff format .` passes
+- [ ] E2E tests pass (if CLI behavior changed): `pytest tests/test_e2e.py`
+
+## Checklist
+
+- [ ] My code follows the project's style guidelines
+- [ ] I have self-reviewed my code
+- [ ] I have updated documentation (README, SKILL.md) if needed
+- [ ] I have added tests for new functionality
+- [ ] All new and existing tests pass
+
+## Screenshots / Output
+
+If applicable, paste relevant CLI output or screenshots here.
+
+## Additional Notes
+
+Anything else reviewers should know.

{scip_cli-2.2.1 → scip_cli-2.4.0}/.pre-commit-config.yaml

@@ -5,6 +5,10 @@ repos:
       - id: ruff
         args: [--fix]
       - id: ruff-format
+  - repo: https://github.com/DetachHead/basedpyright-pre-commit-mirror
+    rev: 1.39.9
+    hooks:
+      - id: basedpyright
   - repo: local
     hooks:
       - id: pytest

scip_cli-2.4.0/CODE_OF_CONDUCT.md

@@ -0,0 +1,128 @@
+# 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, 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 e-mail 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
+ariel.flesler@gmail.com.
+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.0, available at
+https://www.contributor-covenant.org/version/2/0/code_of_conduct.html.
+
+Community Impact Guidelines were inspired by [Mozilla's code of conduct
+enforcement ladder](https://github.com/mozilla/diversity).
+
+[homepage]: https://www.contributor-covenant.org
+
+For answers to common questions about this code of conduct, see the FAQ at
+https://www.contributor-covenant.org/faq. Translations are available at
+https://www.contributor-covenant.org/translations.

scip_cli-2.4.0/CONTRIBUTING.md

@@ -0,0 +1,95 @@
+# Contributing to scip-cli
+
+Thank you for your interest in contributing to scip-cli! This document provides guidelines and information for contributors.
+
+## Code of Conduct
+
+This project adheres to the [Contributor Covenant Code of Conduct](CODE_OF_CONDUCT.md). By participating, you are expected to uphold this code.
+
+## How to Contribute
+
+### Reporting Bugs
+
+Before creating bug reports, please check existing issues. When creating a bug report, include:
+
+- Clear, descriptive title
+- Steps to reproduce the issue
+- Expected vs actual behavior
+- Environment details (OS, Python version, scip-cli version)
+- Minimal reproducible example if possible
+
+### Suggesting Enhancements
+
+Enhancement suggestions are welcome! Please:
+
+- Use a clear, descriptive title
+- Provide a detailed description of the proposed enhancement
+- Explain why this enhancement would be useful
+- Include examples of how it would be used
+
+### Pull Requests
+
+1. Fork the repository
+2. Create a feature branch (`git checkout -b feature/amazing-feature`)
+3. Make your changes
+4. Run tests: `pytest`
+5. Run linter: `ruff check .` and `ruff format .`
+6. Commit your changes (`git commit -m 'Add amazing feature'`)
+7. Push to the branch (`git push origin feature/amazing-feature`)
+8. Open a Pull Request
+
+## Development Setup
+
+```bash
+# Clone your fork
+git clone https://github.com/your-username/scip-cli.git
+cd scip-cli
+
+# Install with dev dependencies
+pip install -e ".[dev]"
+
+# Install pre-commit hooks
+pre-commit install
+
+# Run tests
+pytest
+
+# Run linter
+ruff check .
+ruff format .
+```
+
+## Testing
+
+- Run full test suite: `pytest`
+- Run E2E tests: `pytest tests/test_e2e.py tests/test_e2e_analyze_patterns.py`
+- Integration tests require Node.js and `npx` (for `scip-typescript`)
+
+## Code Style
+
+- Python 3.9+
+- Line length: 120 characters
+- Use type hints where practical
+- Follow existing code patterns
+- No unnecessary comments
+- Use double quotes for strings
+
+## Commit Messages
+
+- Use clear, descriptive commit messages
+- Start with a verb in imperative mood: "Add", "Fix", "Update", "Remove"
+- Keep the first line under 72 characters
+- Reference issues when applicable
+
+## Documentation
+
+- Update README.md for user-facing changes
+- Update SKILL.md if CLI flags or commands change
+- Add docstrings to new functions
+- Keep comments minimal but meaningful
+
+## Questions?
+
+Open an issue or contact the maintainer.
+
+Thank you for contributing!

scip_cli-2.2.1/README.md → scip_cli-2.4.0/PKG-INFO

@@ -1,3 +1,24 @@
+Metadata-Version: 2.4
+Name: scip-cli
+Version: 2.4.0
+Summary: Fast code intelligence via SCIP indexes
+Project-URL: Homepage, https://github.com/flesler/scip-cli
+Author: Ariel Flesler
+License: MIT
+License-File: LICENSE
+Classifier: License :: OSI Approved :: MIT License
+Classifier: Operating System :: OS Independent
+Classifier: Programming Language :: Python :: 3
+Classifier: Topic :: Software Development :: Code Generators
+Requires-Python: >=3.9
+Provides-Extra: dev
+Requires-Dist: basedpyright>=1.39.9; extra == 'dev'
+Requires-Dist: build>=1; extra == 'dev'
+Requires-Dist: pre-commit>=4.0; extra == 'dev'
+Requires-Dist: pytest>=7; extra == 'dev'
+Requires-Dist: ruff>=0.11; extra == 'dev'
+Description-Content-Type: text/markdown
+
 # scip-cli
 
 [![PyPI version](https://badge.fury.io/py/scip-cli.svg)](https://badge.fury.io/py/scip-cli)
@@ -59,7 +80,7 @@ python -m venv .venv && source .venv/bin/activate
 pip install -e ".[dev]"
 ```
 
-Tests and lint: `pytest`, `ruff check .` from the same environment.
+Tests and lint: `pytest`, `ruff check .`, `basedpyright scip_cli/` from the same environment (or `scripts/test.sh` for the publish gate).
 
 ### 2. Install prerequisites (optional)
 
@@ -113,6 +134,7 @@ scip-cli <command> [arguments]
 - `search <pattern>` - Search symbols by name pattern (`--path`)
 - `symbols <file>` - List all symbols in a file (`--path`; bare filename OK)
 - `rdeps <file>` - Find files that depend on a file (`--path`)
+- `deps <symbol|file>` - Find outbound dependencies (what a symbol or file calls) (`--path`, `--paths-only`)
 - `members <symbol>` - List members of a class/interface (`--path`)
 - `analyze [target]` - SQL health dashboards (`--limit`, `--priority`, `--include-tests`). No target: project-wide; directory or file path; symbol name. See [Finding easy wins with `analyze`](#finding-easy-wins-with-analyze).
 - `reindex` - Force re-indexing of the current project (`--path` to limit scope; repeatable)
@@ -139,6 +161,12 @@ scip-cli symbols helper.ts
 # Find files that import from a module
 scip-cli rdeps src/helper.ts
 
+# Find what a function calls
+scip-cli deps greet
+
+# Find what a file depends on
+scip-cli deps src/helper.ts --paths-only
+
 # List members of a class
 scip-cli members Widget
 
@@ -151,7 +179,7 @@ scip-cli skill ~/.claude/skills/scip-cli/SKILL.md
 
 ### Pipelines
 
-Stdout is one record per line; stderr carries warnings and ambiguity notices. Kinds are lowercase (`function`, `class`, `method`, `property`). Pipe-friendly flags: `refs --paths-only`, `search --names-only` / `--paths-only`, `members --names-only`. `rdeps` already prints bare file paths.
+Stdout is one record per line; stderr carries warnings and ambiguity notices. Kinds are lowercase (`function`, `class`, `method`, `property`). Pipe-friendly flags: `refs --paths-only`, `search --names-only` / `--paths-only`, `members --names-only`, `deps --paths-only`. `rdeps` already prints bare file paths.
 
 ```bash
 # What do importers of this file export?
@@ -165,6 +193,9 @@ scip-cli search Handler --kind class --names-only | xargs -I{} scip-cli members
 
 # Walk class members to their definitions
 scip-cli members Widget --names-only | xargs -I{} scip-cli code Widget.{}
+
+# Find all files that a symbol depends on (outbound dependencies)
+scip-cli deps greet --paths-only | sort -u
 ```
 
 ## How It Works
@@ -250,7 +281,7 @@ scip-cli analyze scip_cli --limit 15              # directory: scoped project +
 
 **Defaults:** project-wide and directory analyze skip `tests/`, `*.test.*`, `*.spec.*`, `conftest.py`, and `__tests__/`. Pass `--include-tests` to include them. File-target analyze always includes that file.
 
-**Limits:** “Dead export” means no cross-file mentions in the index — not unreachable code. Same-file private helpers are expected. Re-run `reindex` after large changes; the index is a snapshot.
+**Limits:** "Dead export" means no cross-file mentions in the index — not unreachable code. Same-file private helpers are expected. Re-run `reindex` after large changes; the index is a snapshot.
 
 ## Performance
 
@@ -312,6 +343,14 @@ SCIP_CLI_DEBUG=1 scip-cli refs MyFunction
 
 This is useful for testing and debugging SQL queries
 
+## Contributing
+
+Contributions are welcome! See [CONTRIBUTING.md](CONTRIBUTING.md) for guidelines. By participating, you agree to the [Code of Conduct](CODE_OF_CONDUCT.md).
+
+## Security
+
+To report a security vulnerability, see [SECURITY.md](SECURITY.md).
+
 ## License
 
 MIT

scip_cli-2.2.1/PKG-INFO → scip_cli-2.4.0/README.md

@@ -1,23 +1,3 @@
-Metadata-Version: 2.4
-Name: scip-cli
-Version: 2.2.1
-Summary: Fast code intelligence via SCIP indexes
-Project-URL: Homepage, https://github.com/flesler/scip-cli
-Author: Ariel Flesler
-License: MIT
-License-File: LICENSE
-Classifier: License :: OSI Approved :: MIT License
-Classifier: Operating System :: OS Independent
-Classifier: Programming Language :: Python :: 3
-Classifier: Topic :: Software Development :: Code Generators
-Requires-Python: >=3.9
-Provides-Extra: dev
-Requires-Dist: build>=1; extra == 'dev'
-Requires-Dist: pre-commit>=4.0; extra == 'dev'
-Requires-Dist: pytest>=7; extra == 'dev'
-Requires-Dist: ruff>=0.11; extra == 'dev'
-Description-Content-Type: text/markdown
-
 # scip-cli
 
 [![PyPI version](https://badge.fury.io/py/scip-cli.svg)](https://badge.fury.io/py/scip-cli)
@@ -79,7 +59,7 @@ python -m venv .venv && source .venv/bin/activate
 pip install -e ".[dev]"
 ```
 
-Tests and lint: `pytest`, `ruff check .` from the same environment.
+Tests and lint: `pytest`, `ruff check .`, `basedpyright scip_cli/` from the same environment (or `scripts/test.sh` for the publish gate).
 
 ### 2. Install prerequisites (optional)
 
@@ -133,6 +113,7 @@ scip-cli <command> [arguments]
 - `search <pattern>` - Search symbols by name pattern (`--path`)
 - `symbols <file>` - List all symbols in a file (`--path`; bare filename OK)
 - `rdeps <file>` - Find files that depend on a file (`--path`)
+- `deps <symbol|file>` - Find outbound dependencies (what a symbol or file calls) (`--path`, `--paths-only`)
 - `members <symbol>` - List members of a class/interface (`--path`)
 - `analyze [target]` - SQL health dashboards (`--limit`, `--priority`, `--include-tests`). No target: project-wide; directory or file path; symbol name. See [Finding easy wins with `analyze`](#finding-easy-wins-with-analyze).
 - `reindex` - Force re-indexing of the current project (`--path` to limit scope; repeatable)
@@ -159,6 +140,12 @@ scip-cli symbols helper.ts
 # Find files that import from a module
 scip-cli rdeps src/helper.ts
 
+# Find what a function calls
+scip-cli deps greet
+
+# Find what a file depends on
+scip-cli deps src/helper.ts --paths-only
+
 # List members of a class
 scip-cli members Widget
 
@@ -171,7 +158,7 @@ scip-cli skill ~/.claude/skills/scip-cli/SKILL.md
 
 ### Pipelines
 
-Stdout is one record per line; stderr carries warnings and ambiguity notices. Kinds are lowercase (`function`, `class`, `method`, `property`). Pipe-friendly flags: `refs --paths-only`, `search --names-only` / `--paths-only`, `members --names-only`. `rdeps` already prints bare file paths.
+Stdout is one record per line; stderr carries warnings and ambiguity notices. Kinds are lowercase (`function`, `class`, `method`, `property`). Pipe-friendly flags: `refs --paths-only`, `search --names-only` / `--paths-only`, `members --names-only`, `deps --paths-only`. `rdeps` already prints bare file paths.
 
 ```bash
 # What do importers of this file export?
@@ -185,6 +172,9 @@ scip-cli search Handler --kind class --names-only | xargs -I{} scip-cli members
 
 # Walk class members to their definitions
 scip-cli members Widget --names-only | xargs -I{} scip-cli code Widget.{}
+
+# Find all files that a symbol depends on (outbound dependencies)
+scip-cli deps greet --paths-only | sort -u
 ```
 
 ## How It Works
@@ -270,7 +260,7 @@ scip-cli analyze scip_cli --limit 15              # directory: scoped project +
 
 **Defaults:** project-wide and directory analyze skip `tests/`, `*.test.*`, `*.spec.*`, `conftest.py`, and `__tests__/`. Pass `--include-tests` to include them. File-target analyze always includes that file.
 
-**Limits:** “Dead export” means no cross-file mentions in the index — not unreachable code. Same-file private helpers are expected. Re-run `reindex` after large changes; the index is a snapshot.
+**Limits:** "Dead export" means no cross-file mentions in the index — not unreachable code. Same-file private helpers are expected. Re-run `reindex` after large changes; the index is a snapshot.
 
 ## Performance
 
@@ -332,6 +322,14 @@ SCIP_CLI_DEBUG=1 scip-cli refs MyFunction
 
 This is useful for testing and debugging SQL queries
 
+## Contributing
+
+Contributions are welcome! See [CONTRIBUTING.md](CONTRIBUTING.md) for guidelines. By participating, you agree to the [Code of Conduct](CODE_OF_CONDUCT.md).
+
+## Security
+
+To report a security vulnerability, see [SECURITY.md](SECURITY.md).
+
 ## License
 
 MIT

scip_cli-2.4.0/SECURITY.md

@@ -0,0 +1,46 @@
+# Security Policy
+
+## Supported Versions
+
+| Version | Supported          |
+| ------- | ------------------ |
+| latest  | :white_check_mark: |
+| < latest| :x:                |
+
+## Reporting a Vulnerability
+
+**Do not open public issues for security vulnerabilities.**
+
+If you discover a security vulnerability, please email **ariel.flesler@gmail.com** with:
+
+- Description of the vulnerability
+- Steps to reproduce or proof of concept
+- Potential impact
+- Suggested fix (if any)
+
+## What to Expect
+
+- Acknowledgment within 48 hours
+- Assessment of the vulnerability's severity and impact
+- Timeline for a fix and release
+- Credit in the release notes (unless you prefer to remain anonymous)
+
+## Scope
+
+Security considerations for scip-cli include:
+
+- **Index integrity**: SCIP indexes are read from local filesystem and trusted
+- **SQL injection**: All queries use parameterized statements
+- **Path traversal**: File operations are scoped to the indexed project
+- **Dependency security**: Minimal dependencies; pinned versions in `pyproject.toml`
+
+## Security Best Practices for Users
+
+- Install from PyPI: `pip install scip-cli` (verified releases)
+- Keep scip-cli updated to the latest version
+- Review `.scip-cli.json` configuration before use in untrusted projects
+- The `scip` binary is downloaded from [official releases](https://github.com/scip-code/scip/releases)
+
+## Responsible Disclosure
+
+We appreciate responsible disclosure and will work with you to understand and address the issue promptly.

{scip_cli-2.2.1 → scip_cli-2.4.0}/pyproject.toml

@@ -32,6 +32,7 @@ packages = ["scip_cli"]
 [project.optional-dependencies]
 dev = [
     "ruff>=0.11",
+    "basedpyright>=1.39.9",
     "pytest>=7",
     "pre-commit>=4.0",
     "build>=1",
@@ -57,3 +58,20 @@ addopts = "-q --tb=line --no-header"
 markers = [
     "integration: uses the shared indexed TS fixture (requires npx / scip-typescript)",
 ]
+
+[tool.basedpyright]
+pythonVersion = "3.10"
+venvPath = "."
+venv = ".venv"
+include = ["scip_cli"]
+exclude = ["tests"]
+
+# Gradual typing: basedpyright's unknown* rules fire hundreds of times on CLI/SQL glue
+# pythonVersion=3.10 matches union syntax in annotations; package still supports 3.9 via __future__ annotations
+reportAny = "none"
+reportUnknownParameterType = "none"
+reportUnknownArgumentType = "none"
+reportUnknownVariableType = "none"
+reportUnknownMemberType = "none"
+reportMissingParameterType = "none"
+reportUnusedCallResult = "none"