plexavo 0.2.1__tar.gz → 0.2.2__tar.gz

{plexavo-0.2.1 → plexavo-0.2.2}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: plexavo
-Version: 0.2.1
+Version: 0.2.2
 Summary: Open-source AWS misconfiguration scanner — runs with your own local AWS credentials, nothing sent to anyone else.
 Author: Kavee
 License: AGPL-3.0-or-later
@@ -127,20 +127,24 @@ scoped by a Condition block, or a CloudTrail lookup that hit its page cap on
 
 ## Quick start
 
-**Recommended: [uv](https://docs.astral.sh/uv/).** It installs Plexavo into
-its own isolated environment automatically — no venv to create, activate,
-or remember to reactivate in every new terminal.
+The install path depends on your OS — **uv on macOS & Linux**, **pip on
+Windows**. Either way it's a one-command install with no venv to create,
+activate, or reactivate in every new terminal.
 
-### 1. Install uv (if you don't already have it)
+### macOS & Linux — uv
+
+[uv](https://docs.astral.sh/uv/) installs Plexavo into its own isolated
+environment automatically.
+
+**1. Install uv** (if you don't already have it):
 
 ```bash
-curl -LsSf https://astral.sh/uv/install.sh | sh          # Mac/Linux
-powershell -c "irm https://astral.sh/uv/install.ps1 | iex" # Windows
+curl -LsSf https://astral.sh/uv/install.sh | sh
 ```
 
 (Full options: [uv installation docs](https://docs.astral.sh/uv/getting-started/installation/).)
 
-### 2. Install Plexavo
+**2. Install Plexavo:**
 
 ```bash
 uv tool install plexavo
@@ -178,12 +182,60 @@ uv tool upgrade plexavo
 uv tool uninstall plexavo
 ```
 
-### 3. Run a scan
+### Windows — pip
+
+Install with `pip` and run the tool as `py -m plexavo`:
+
+```powershell
+py -m pip install --user plexavo
+py -m plexavo
+```
+
+`py -m plexavo` with no arguments opens the interactive menu, exactly
+like the `plexavo` command does on macOS/Linux — flags are only for
+scripting/CI.
+
+> **Why not uv/pipx on Windows?** Both work by putting a small generated
+> `plexavo.exe` launcher on your PATH. That launcher is unsigned, and
+> Windows Smart App Control blocks unsigned executables it doesn't
+> recognise — so `plexavo` can fail to start with a "can't confirm who
+> published" message. `py -m plexavo` calls Python directly and never
+> touches that launcher, so it always works. (If your machine doesn't
+> enforce Smart App Control, `uv tool install plexavo` works here too.)
+
+**AI-narrated explanations** (see [Cost](#cost)):
+
+```powershell
+py -m pip install --user "plexavo[ai]"
+```
+
+Updating or removing later:
+
+```powershell
+py -m pip install --user --upgrade plexavo
+py -m pip uninstall plexavo
+```
+
+### Optional: type `plexavo` instead of `py -m plexavo`
+
+Add a shortcut to your PowerShell profile once:
+
+```powershell
+Add-Content $PROFILE 'function plexavo { py -m plexavo @args }'
+```
+
+Open a new terminal and `plexavo` then works just like it does on
+macOS/Linux.
+
+### Run a scan
 
 ```bash
 plexavo scan --profile my-aws-profile --report-html report.html
 ```
 
+(On Windows without the shortcut above: `py -m plexavo scan --profile
+my-aws-profile --report-html report.html`.)
+
 No `--profile`? It uses your default profile / environment variables,
 same resolution order as the AWS CLI. No AI, no API key, no cost — and
 findings still come with free Next Step / Full Fix Detail guidance
@@ -213,19 +265,24 @@ plexavo scan --profile my-aws-profile --explain --report-html report.html --repo
 
 ### Alternative: pipx
 
-Already use [pipx](https://pipx.pypa.io/)? It works exactly the same way —
-its own isolated environment, one global command, no venv:
+Already use [pipx](https://pipx.pypa.io/) on macOS/Linux? It works exactly
+the same way as uv — its own isolated environment, one global command, no
+venv:
 
 ```bash
 pipx install plexavo
 pipx install "plexavo[ai]"   # with AI-narrated explanations
 ```
 
+On Windows, pipx has the same Smart App Control caveat as uv (see the
+Windows section above) — if the `plexavo` command is blocked, run
+`py -m plexavo` instead, or use the `pip` install.
+
 ### Alternative: pip + venv
 
-Prefer to manage the environment yourself, or on a system without uv/pipx?
-Modern Python (PEP 668) blocks a plain `pip install` outside a venv on
-many systems, so create one first:
+Want full isolation and prefer to manage the environment yourself? Modern
+Python (PEP 668) blocks a plain `pip install` outside a venv on many
+Linux and Homebrew setups, so create one first:
 
 ```bash
 python -m venv plexavo-env
@@ -238,7 +295,9 @@ pip install "plexavo[ai]"   # with AI-narrated explanations
 
 You'll need to reactivate this venv (`plexavo-env\Scripts\activate` /
 `source plexavo-env/bin/activate`) every time you open a new terminal —
-`deactivate` exits it without uninstalling anything.
+`deactivate` exits it without uninstalling anything. On Windows, run
+`python -m plexavo` if the `plexavo` command is blocked by Smart App
+Control.
 
 ### From source (for contributing, or trying an unreleased change)
 
@@ -257,6 +316,7 @@ plexavo/
 ├── findings.py                  # Finding data model, Severity enum
 ├── scoring.py                    # 0-100 score from a list of Findings
 ├── cli.py                         # `plexavo scan ...` entry point
+├── __main__.py                      # lets `python -m plexavo` run the CLI
 ├── checks/
 │   ├── iam.py                       # IAM-01 to IAM-06 (privilege escalation)
 │   ├── iam_hygiene.py                # IAM-07 to IAM-14 (hygiene, cross-account trust)

{plexavo-0.2.1 → plexavo-0.2.2}/README.md

@@ -98,20 +98,24 @@ scoped by a Condition block, or a CloudTrail lookup that hit its page cap on
 
 ## Quick start
 
-**Recommended: [uv](https://docs.astral.sh/uv/).** It installs Plexavo into
-its own isolated environment automatically — no venv to create, activate,
-or remember to reactivate in every new terminal.
+The install path depends on your OS — **uv on macOS & Linux**, **pip on
+Windows**. Either way it's a one-command install with no venv to create,
+activate, or reactivate in every new terminal.
 
-### 1. Install uv (if you don't already have it)
+### macOS & Linux — uv
+
+[uv](https://docs.astral.sh/uv/) installs Plexavo into its own isolated
+environment automatically.
+
+**1. Install uv** (if you don't already have it):
 
 ```bash
-curl -LsSf https://astral.sh/uv/install.sh | sh          # Mac/Linux
-powershell -c "irm https://astral.sh/uv/install.ps1 | iex" # Windows
+curl -LsSf https://astral.sh/uv/install.sh | sh
 ```
 
 (Full options: [uv installation docs](https://docs.astral.sh/uv/getting-started/installation/).)
 
-### 2. Install Plexavo
+**2. Install Plexavo:**
 
 ```bash
 uv tool install plexavo
@@ -149,12 +153,60 @@ uv tool upgrade plexavo
 uv tool uninstall plexavo
 ```
 
-### 3. Run a scan
+### Windows — pip
+
+Install with `pip` and run the tool as `py -m plexavo`:
+
+```powershell
+py -m pip install --user plexavo
+py -m plexavo
+```
+
+`py -m plexavo` with no arguments opens the interactive menu, exactly
+like the `plexavo` command does on macOS/Linux — flags are only for
+scripting/CI.
+
+> **Why not uv/pipx on Windows?** Both work by putting a small generated
+> `plexavo.exe` launcher on your PATH. That launcher is unsigned, and
+> Windows Smart App Control blocks unsigned executables it doesn't
+> recognise — so `plexavo` can fail to start with a "can't confirm who
+> published" message. `py -m plexavo` calls Python directly and never
+> touches that launcher, so it always works. (If your machine doesn't
+> enforce Smart App Control, `uv tool install plexavo` works here too.)
+
+**AI-narrated explanations** (see [Cost](#cost)):
+
+```powershell
+py -m pip install --user "plexavo[ai]"
+```
+
+Updating or removing later:
+
+```powershell
+py -m pip install --user --upgrade plexavo
+py -m pip uninstall plexavo
+```
+
+### Optional: type `plexavo` instead of `py -m plexavo`
+
+Add a shortcut to your PowerShell profile once:
+
+```powershell
+Add-Content $PROFILE 'function plexavo { py -m plexavo @args }'
+```
+
+Open a new terminal and `plexavo` then works just like it does on
+macOS/Linux.
+
+### Run a scan
 
 ```bash
 plexavo scan --profile my-aws-profile --report-html report.html
 ```
 
+(On Windows without the shortcut above: `py -m plexavo scan --profile
+my-aws-profile --report-html report.html`.)
+
 No `--profile`? It uses your default profile / environment variables,
 same resolution order as the AWS CLI. No AI, no API key, no cost — and
 findings still come with free Next Step / Full Fix Detail guidance
@@ -184,19 +236,24 @@ plexavo scan --profile my-aws-profile --explain --report-html report.html --repo
 
 ### Alternative: pipx
 
-Already use [pipx](https://pipx.pypa.io/)? It works exactly the same way —
-its own isolated environment, one global command, no venv:
+Already use [pipx](https://pipx.pypa.io/) on macOS/Linux? It works exactly
+the same way as uv — its own isolated environment, one global command, no
+venv:
 
 ```bash
 pipx install plexavo
 pipx install "plexavo[ai]"   # with AI-narrated explanations
 ```
 
+On Windows, pipx has the same Smart App Control caveat as uv (see the
+Windows section above) — if the `plexavo` command is blocked, run
+`py -m plexavo` instead, or use the `pip` install.
+
 ### Alternative: pip + venv
 
-Prefer to manage the environment yourself, or on a system without uv/pipx?
-Modern Python (PEP 668) blocks a plain `pip install` outside a venv on
-many systems, so create one first:
+Want full isolation and prefer to manage the environment yourself? Modern
+Python (PEP 668) blocks a plain `pip install` outside a venv on many
+Linux and Homebrew setups, so create one first:
 
 ```bash
 python -m venv plexavo-env
@@ -209,7 +266,9 @@ pip install "plexavo[ai]"   # with AI-narrated explanations
 
 You'll need to reactivate this venv (`plexavo-env\Scripts\activate` /
 `source plexavo-env/bin/activate`) every time you open a new terminal —
-`deactivate` exits it without uninstalling anything.
+`deactivate` exits it without uninstalling anything. On Windows, run
+`python -m plexavo` if the `plexavo` command is blocked by Smart App
+Control.
 
 ### From source (for contributing, or trying an unreleased change)
 
@@ -228,6 +287,7 @@ plexavo/
 ├── findings.py                  # Finding data model, Severity enum
 ├── scoring.py                    # 0-100 score from a list of Findings
 ├── cli.py                         # `plexavo scan ...` entry point
+├── __main__.py                      # lets `python -m plexavo` run the CLI
 ├── checks/
 │   ├── iam.py                       # IAM-01 to IAM-06 (privilege escalation)
 │   ├── iam_hygiene.py                # IAM-07 to IAM-14 (hygiene, cross-account trust)

{plexavo-0.2.1 → plexavo-0.2.2}/plexavo/__init__.py

@@ -4,4 +4,4 @@ Runs entirely with your own local AWS credentials. Nothing is sent to
 anyone else. See README.md for usage, or `plexavo scan --help`.
 """
 
-__version__ = "0.2.1"
+__version__ = "0.2.2"

plexavo-0.2.2/plexavo/__main__.py

@@ -0,0 +1,13 @@
+"""Allow `python -m plexavo` (and `py -m plexavo` on Windows) to launch the CLI.
+
+This is the exact same entry point as the installed `plexavo` command, so
+running it with no arguments still opens the interactive menu. It exists so
+Windows users can install with plain `pip` and run the tool without going
+through the generated `plexavo.exe` launcher, which Windows Smart App Control
+blocks on some machines (it's unsigned). See the README's Quick start.
+"""
+
+from plexavo.cli import main
+
+if __name__ == "__main__":
+    main()

{plexavo-0.2.1 → plexavo-0.2.2}/plexavo.egg-info/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: plexavo
-Version: 0.2.1
+Version: 0.2.2
 Summary: Open-source AWS misconfiguration scanner — runs with your own local AWS credentials, nothing sent to anyone else.
 Author: Kavee
 License: AGPL-3.0-or-later
@@ -127,20 +127,24 @@ scoped by a Condition block, or a CloudTrail lookup that hit its page cap on
 
 ## Quick start
 
-**Recommended: [uv](https://docs.astral.sh/uv/).** It installs Plexavo into
-its own isolated environment automatically — no venv to create, activate,
-or remember to reactivate in every new terminal.
+The install path depends on your OS — **uv on macOS & Linux**, **pip on
+Windows**. Either way it's a one-command install with no venv to create,
+activate, or reactivate in every new terminal.
 
-### 1. Install uv (if you don't already have it)
+### macOS & Linux — uv
+
+[uv](https://docs.astral.sh/uv/) installs Plexavo into its own isolated
+environment automatically.
+
+**1. Install uv** (if you don't already have it):
 
 ```bash
-curl -LsSf https://astral.sh/uv/install.sh | sh          # Mac/Linux
-powershell -c "irm https://astral.sh/uv/install.ps1 | iex" # Windows
+curl -LsSf https://astral.sh/uv/install.sh | sh
 ```
 
 (Full options: [uv installation docs](https://docs.astral.sh/uv/getting-started/installation/).)
 
-### 2. Install Plexavo
+**2. Install Plexavo:**
 
 ```bash
 uv tool install plexavo
@@ -178,12 +182,60 @@ uv tool upgrade plexavo
 uv tool uninstall plexavo
 ```
 
-### 3. Run a scan
+### Windows — pip
+
+Install with `pip` and run the tool as `py -m plexavo`:
+
+```powershell
+py -m pip install --user plexavo
+py -m plexavo
+```
+
+`py -m plexavo` with no arguments opens the interactive menu, exactly
+like the `plexavo` command does on macOS/Linux — flags are only for
+scripting/CI.
+
+> **Why not uv/pipx on Windows?** Both work by putting a small generated
+> `plexavo.exe` launcher on your PATH. That launcher is unsigned, and
+> Windows Smart App Control blocks unsigned executables it doesn't
+> recognise — so `plexavo` can fail to start with a "can't confirm who
+> published" message. `py -m plexavo` calls Python directly and never
+> touches that launcher, so it always works. (If your machine doesn't
+> enforce Smart App Control, `uv tool install plexavo` works here too.)
+
+**AI-narrated explanations** (see [Cost](#cost)):
+
+```powershell
+py -m pip install --user "plexavo[ai]"
+```
+
+Updating or removing later:
+
+```powershell
+py -m pip install --user --upgrade plexavo
+py -m pip uninstall plexavo
+```
+
+### Optional: type `plexavo` instead of `py -m plexavo`
+
+Add a shortcut to your PowerShell profile once:
+
+```powershell
+Add-Content $PROFILE 'function plexavo { py -m plexavo @args }'
+```
+
+Open a new terminal and `plexavo` then works just like it does on
+macOS/Linux.
+
+### Run a scan
 
 ```bash
 plexavo scan --profile my-aws-profile --report-html report.html
 ```
 
+(On Windows without the shortcut above: `py -m plexavo scan --profile
+my-aws-profile --report-html report.html`.)
+
 No `--profile`? It uses your default profile / environment variables,
 same resolution order as the AWS CLI. No AI, no API key, no cost — and
 findings still come with free Next Step / Full Fix Detail guidance
@@ -213,19 +265,24 @@ plexavo scan --profile my-aws-profile --explain --report-html report.html --repo
 
 ### Alternative: pipx
 
-Already use [pipx](https://pipx.pypa.io/)? It works exactly the same way —
-its own isolated environment, one global command, no venv:
+Already use [pipx](https://pipx.pypa.io/) on macOS/Linux? It works exactly
+the same way as uv — its own isolated environment, one global command, no
+venv:
 
 ```bash
 pipx install plexavo
 pipx install "plexavo[ai]"   # with AI-narrated explanations
 ```
 
+On Windows, pipx has the same Smart App Control caveat as uv (see the
+Windows section above) — if the `plexavo` command is blocked, run
+`py -m plexavo` instead, or use the `pip` install.
+
 ### Alternative: pip + venv
 
-Prefer to manage the environment yourself, or on a system without uv/pipx?
-Modern Python (PEP 668) blocks a plain `pip install` outside a venv on
-many systems, so create one first:
+Want full isolation and prefer to manage the environment yourself? Modern
+Python (PEP 668) blocks a plain `pip install` outside a venv on many
+Linux and Homebrew setups, so create one first:
 
 ```bash
 python -m venv plexavo-env
@@ -238,7 +295,9 @@ pip install "plexavo[ai]"   # with AI-narrated explanations
 
 You'll need to reactivate this venv (`plexavo-env\Scripts\activate` /
 `source plexavo-env/bin/activate`) every time you open a new terminal —
-`deactivate` exits it without uninstalling anything.
+`deactivate` exits it without uninstalling anything. On Windows, run
+`python -m plexavo` if the `plexavo` command is blocked by Smart App
+Control.
 
 ### From source (for contributing, or trying an unreleased change)
 
@@ -257,6 +316,7 @@ plexavo/
 ├── findings.py                  # Finding data model, Severity enum
 ├── scoring.py                    # 0-100 score from a list of Findings
 ├── cli.py                         # `plexavo scan ...` entry point
+├── __main__.py                      # lets `python -m plexavo` run the CLI
 ├── checks/
 │   ├── iam.py                       # IAM-01 to IAM-06 (privilege escalation)
 │   ├── iam_hygiene.py                # IAM-07 to IAM-14 (hygiene, cross-account trust)

{plexavo-0.2.1 → plexavo-0.2.2}/plexavo.egg-info/SOURCES.txt

@@ -2,6 +2,7 @@ LICENSE
 README.md
 pyproject.toml
 plexavo/__init__.py
+plexavo/__main__.py
 plexavo/auth.py
 plexavo/aws_profile_setup.py
 plexavo/cli.py
@@ -35,6 +36,7 @@ plexavo/report/fonts/GEIST-FONT-LICENSE.txt
 plexavo/report/templates/report.html.j2
 tests/test_ai_narration_offline.py
 tests/test_auth_offline.py
+tests/test_cli_entrypoint.py
 tests/test_encryption_offline.py
 tests/test_iam_hygiene_offline.py
 tests/test_iam_offline.py

{plexavo-0.2.1 → plexavo-0.2.2}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "plexavo"
-version = "0.2.1"
+version = "0.2.2"
 description = "Open-source AWS misconfiguration scanner — runs with your own local AWS credentials, nothing sent to anyone else."
 readme = "README.md"
 license = { text = "AGPL-3.0-or-later" }

plexavo-0.2.2/tests/test_cli_entrypoint.py

@@ -0,0 +1,50 @@
+"""Checks that `python -m plexavo` works and is equivalent to the installed
+`plexavo` command / `python -m plexavo.cli`.
+
+This is the Windows install path (README Quick start): install with pip, run
+via `py -m plexavo` instead of the Smart-App-Control-blocked `plexavo.exe`
+launcher. If the `plexavo/__main__.py` shim regresses, that path breaks.
+
+Run: python test_cli_entrypoint.py
+"""
+
+import subprocess
+import sys
+
+failures = 0
+
+
+def assert_true(cond, msg):
+    global failures
+    status = "PASS" if cond else "FAIL"
+    print(f"[{status}] {msg}")
+    if not cond:
+        failures += 1
+
+
+def run(*args):
+    return subprocess.run(
+        [sys.executable, *args],
+        capture_output=True,
+        text=True,
+    )
+
+
+print("=== python -m plexavo --version ===")
+mod = run("-m", "plexavo", "--version")
+assert_true(mod.returncode == 0, f"exits 0 (got {mod.returncode}, stderr: {mod.stderr!r})")
+assert_true("plexavo" in (mod.stdout + mod.stderr).lower(), "prints the version string")
+
+print("\n=== equivalent to python -m plexavo.cli ===")
+cli = run("-m", "plexavo.cli", "--version")
+assert_true(mod.stdout == cli.stdout, f"same --version output ({mod.stdout!r} vs {cli.stdout!r})")
+
+print("\n=== python -m plexavo --help mentions the scan subcommand ===")
+helptext = run("-m", "plexavo", "--help")
+assert_true(helptext.returncode == 0, f"--help exits 0 (got {helptext.returncode})")
+assert_true("scan" in helptext.stdout, "help lists the scan subcommand")
+assert_true("usage: plexavo" in helptext.stdout,
+            "usage line shows 'plexavo', not '__main__.py'")
+
+print(f"\n{'ALL PASSED' if failures == 0 else f'{failures} FAILURE(S)'}")
+sys.exit(1 if failures else 0)