veny
PulseGate's liveness check found it on 3 Oct 2026; it is registered on GitHub and PyPI and has been in the index since 23 Aug 2026. How this is checked
veny is an open-source command-line tool that runs a Python script inside a virtual environment generated from the script’s imports. It is intended for Python developers who want lightweight dependency isolation without manually creating an environment.
Inferred · not functionally tested
Overview
5 featuresPurpose: Creating isolated Python environments for scripts without manually identifying and installing their dependencies.
Inferred · not functionally tested
Audience: Python developers
Inferred · not functionally tested
Functions: Unknown
Interfaces: API: unknown · MCP: unknown · CLI: indicated (inferred, not tested) · Self-hosting: indicated (inferred, not tested)
Recorded constraints: pricing: open_source · license: Apache-2.0 · platforms: CLI · deployment: cli, self_hosted
Constraint provenance is unknown; confirm requirements with the publisher.
Record sources: pypi.org · github.com. These links do not verify the individual claims.
In the CLI tools & terminal space, veny takes a focused approach. Inferred · not functionally tested: It focuses on creating isolated Python environments for scripts without manually identifying and installing their dependencies. Inferred · not functionally tested: veny is an open-source project aimed at python developers. Basis unknown · not verified: The project is open source (Apache-2.0). Basis unknown · not verified: veny is available on the command line, and it can be self-hosted.
killett builds and maintains veny, and it first shipped in 2024. The project is developed in the open on GitHub with 343 commits in the last 90 days. Inferred · not functionally tested: Among its 5 catalogued features are import detection, virtual environment creation, and script execution.
Summary written by a language model from the project’s public pages.
Tasks: Inferred · not functionally tested
- Import detection
- Virtual environment creation
- Script execution
- Dependency installation
- Apache-2.0 license
Topics: Inferred · not functionally tested
Built with & integrations
Trust & compliance
Indexing history
1What PulseGate has recorded for this listing
Frequently asked questions about veny
- What is veny?
- Inferred · not functionally tested: Veny focuses on creating isolated Python environments for scripts without manually identifying and installing their dependencies. It is catalogued under CLI tools & terminal on PulseGate.
- Who should use veny?
- Inferred · not functionally tested: veny is an open-source project built for python developers.
- Is veny free?
- Basis unknown · not verified: Yes — veny is open source under the Apache-2.0 license and free to use.
- What platforms does veny run on?
- Basis unknown · not verified: veny runs on the command line. It can also be self-hosted.
- Is veny still active?
- PulseGate's liveness check found it on 3 Oct 2026. Its GitHub repository shows 343 commits in the last 90 days.
- Who develops veny?
- veny is developed by killett.
- When did veny launch?
- veny first shipped in 2024.
- Is veny open source?
- Basis unknown · not verified: Yes — veny is open source under the Apache-2.0 license, developed on GitHub.
Similar projects
Closest matches by what these projects do