CodeVetter · Repo Unpack · Risk map
python-poetry/poetry
The main sensitive boundaries are plugin imports, backend execution, credentials, remote artifacts, and writes into Python environments. Source contains guards for credential scheme handling, archive hashes, and installation paths, alongside deliberate compatibility exceptions. Persistence and environment updates occur in separate steps, which deserves attention during failure-path changes. These are source observations or labeled hypotheses, not confirmed vulnerabilities or an exhaustive security audit.
- Plugin loading executes entry-point classes inside Poetry's process; existing project plugin paths are prepended and passed to addsitedir, which processes .pth files, unless application plugin loading is disabled.
- Package builds invoke backend subprocesses in ephemeral environments, and editable root builds can execute a configured build script via env.run; environment isolation here does not document an OS security sandbox.
- PasswordManager falls back to plaintext auth configuration when keyring is unavailable or disabled, with a warning; credential-storage changes therefore affect user-level sensitive state.
- Authenticator scopes configured credentials to host and chooses among same-host repositories by path affinity; it rejects HTTPS-configured credentials for non-HTTPS requests, but certificate configuration can explicitly disable verification.
- Archive hash validation is conditional on package.files; when present, missing filenames, unusable hash algorithms, or mismatches fail. Wheel RECORD content validation is disabled and validation issues are collected rather than immediately rejecting the wheel.
- Environment writes extend outside the checkout, including the system environment when virtualenv creation is disabled; WheelDestination checks target containment but permits overwriting existing files with a warning.
- Hypothesis: interrupted operations can leave partially changed environments or mismatched project/lock state because builtin uninstall removes without rollback, lock writing is direct, and add writes project TOML after installation/lock work. (inferred)
- Transaction deliberately treats some index source changes as equivalent: switching between PyPI and legacy sources can produce no update when installed source metadata is absent; provenance-sensitive changes must preserve or reassess this compatibility branch.