2 Commits

Include renames

Author	SHA1	Message	Date
3 people	648adcbda4	feat: add uvx (uv tool run) package executor (#357) ... * feat(uvx): add uvx (uv tool run) package executor Adds support for `uvx`, implemented as a PyPI Executor alongside pipx. uvx is an alias for `uv tool run`: it installs a tool into an ephemeral environment and runs it, so it has no install/list subcommand and the first positional argument (or --from) is the package to audit. Parsing highlights: - --from overrides the positional command as the package to audit - --with packages are audited as additional environment dependencies - name@version shorthand (ruff@0.3.0, ruff@latest) is normalized - flag parsing stops at the tool name so the tool's own flags are not misread as uvx options; uvx's value/boolean flags are registered so none greedily consume the package positional - VCS/URL/local-path specs are skipped for registry auditing Wires up command registration, analytics, shell alias/shim, cloud audit mapping, a dedicated `uvx` sandbox profile (UV_*/PIP_* env, uv cache and tool dirs), config policy, docs, unit tests and an E2E workflow step. Closes #326 https://claude.ai/code/session_011hyLxq7oWJX5Dp4tCEfG19 * chore(uvx): align docs and base profile with uvx support Incorporates the low-risk, non-parser improvements from the community PR #345 (author non-responsive) into our implementation: - list uvx (and the previously-missing pipx) as PyPI managers in the pypi-restrictive base profile package_managers and its README, so the base profile applies directly when selected via --sandbox-profile - document uvx in docs/github-action.md and docs/proxy-mode.md - add version / IsExplicitVersion assertions to the uvx parser tests Our pflag-based parser is kept as-is: unlike #345 it audits --with packages and handles all uvx short flags (e.g. -w), both of which the community PR misses. * fix(uvx): skip interpreter requests; use require in tests Addresses review feedback on PR #357: - uvx interpreter requests (`uvx python`, `uvx python@3.12`, `uvx pypy`, ...) launch an isolated interpreter rather than installing a PyPI tool. Treating the positional as a package made the guard flow resolve/analyze pkg:pypi/python (and python==3.12), which could wrongly block or fail a valid invocation. Skip these for the positional; --with packages on the same command are still audited. - Use require.NoError / require.Len for fatal assertions in the uvx tests, matching the repo's testing convention, so a failure stops the subtest before a nil dereference instead of panicking. * docs(uvx): document fail-open and --with-requirements trade-offs Record the two deliberate parsing decisions raised in review as in-code trade-off comments (no behavior change): - unknown flags are tolerated (fail open), consistent with the other executors; the residual gap only affects non-proxy guard mode since the default proxy flow intercepts every registry download. - --with-requirements / --with-editable values are consumed but not expanded into audit targets; expanding them needs manifest-extractor and guard changes, tracked as follow-up. Proxy mode still covers them. * docs(uvx): drop --with-requirements limitation note Per maintainer review: guard mode is being deprecated and auditing the contents of an existing requirements file is a scanner's responsibility, not PMG's. Remove the "known limitation / follow-up" note; the flags stay registered only so their values are not mistaken for the tool positional. --------- Co-authored-by: Claude <noreply@anthropic.com>	2026-07-02 18:49:31 +05:30
3 people	46cc70db53	feat: add GitHub Action for one-step PMG setup in CI (#263) ... * feat: add GitHub Action for one-step PMG setup in CI Composite action at repo root that downloads PMG (with SHA-256 verification against the upstream checksums.txt), runs `pmg setup install`, and wires shims onto $GITHUB_PATH so subsequent `npm install` / `pip install` calls are transparently analyzed. Defaults are conservative: malware blocking + dependency cooldown + proxy mode (matching PMG's own defaults). Sandbox is opt-in because enabling Landlock/Bubblewrap on ubuntu-latest requires relaxing AppArmor user-namespace restrictions. Cloud sync uses the documented SAFEDEP_API_KEY / SAFEDEP_TENANT_ID env-var fallback so we skip the keychain codepath that has no usable backend in headless CI. When cloud is enabled and no endpoint-id is supplied, the action sets PMG_CLOUD_ENDPOINT_ID=github-actions/${GITHUB_REPOSITORY} so events aggregate per repository instead of per ephemeral runner hostname. Closes #248. https://claude.ai/code/session_01ARb8ZiBiJjvhWjchBXraAh * fix(action): drop github.repository template from input description Action manifest validation rejected the action.yml because the endpoint-id input description contained ${{ github.repository }} — template expressions aren't evaluated in input description text and trip the validator with "Unrecognized named-value: 'github'". This caused every job using uses: ./ to fail before any step ran. Also switch the config-file e2e job to verify the staged file directly instead of calling `pmg config get`, which is not in the v0.13.0 release that "latest" resolves to today. https://claude.ai/code/session_01ARb8ZiBiJjvhWjchBXraAh * fix(action): address review comments on PR #263 - Drop opinionated defaults on PMG_* toggle inputs. All defaults are now empty strings, and the action only exports PMG_* env vars when the caller explicitly sets the input. Without this, defaults like PMG_PARANOID=false silently shadowed config-file overrides because env vars beat config.yml in Viper precedence. - Verify cached PMG against upstream checksums.txt on every cache hit. The cached tarball is stored alongside the binary and re-hashed against the freshly-fetched checksums.txt; on drift, the cache entry is evicted and re-downloaded. - Export PMG_* env vars BEFORE running `pmg setup install` so settings like disable-telemetry actually apply during setup, not just to subsequent package-manager calls. - Add `|| true` to the grep that extracts the expected checksum so set -e doesn't kill the script before the friendly error message fires when no checksum entry is found. - Pin third-party actions (actions/checkout, actions/setup-node) to commit SHAs to match the repo's supply-chain hardening convention. - Fix the malicious-package E2E test capturing tee's exit code instead of npm's; redirect to a file and check the actual command exit code. - Add an E2E job that asserts PMG_PARANOID is unset when only config-file is provided — regression guard for the precedence fix. https://claude.ai/code/session_01ARb8ZiBiJjvhWjchBXraAh * ci(action-e2e): scope sandbox tests to action setup, not PMG runtime The landlock job was running `npm install express` with no explicit sandbox profile and the default profile blocks something npm needs (PMG's own e2e uses `--sandbox-profile npm-restrictive` to make this viable). Bubblewrap happened to pass, but verifying the default sandbox profile is permissive enough for arbitrary package installs is PMG's e2e responsibility — this workflow's job is to assert the action wires sandbox config correctly. Switch both drivers to a matrix and verify only what the action owns: PMG_SANDBOX_* env vars propagated, pmg binary runs, bwrap is installed when requested, AppArmor user-ns restriction relaxed. https://claude.ai/code/session_01ARb8ZiBiJjvhWjchBXraAh * ci(action-e2e): bump setup-node to 24 Node 20 reached end-of-life and setup-node now warns on it. Match the version pinned by publish-npm.yml (the repo's newest workflow). Updated the README and docs/github-action.md quick-start examples to match. https://claude.ai/code/session_01ARb8ZiBiJjvhWjchBXraAh --------- Co-authored-by: Claude <noreply@anthropic.com>	2026-05-18 00:44:06 +05:30