pun
This is a pun.
Table of Contents
- Screenshots
- Installation
- Usage
- Support
- Motivation
- Features
- About
- Author
- Analysis
- Contributing
- Development
- Releasing
- Credits
- License
- Changelog
Screenshots
Installation
pun is a standalone end-user tool whose primary command is pun. Install it into an isolated environment:
uv tool install pun
Or run it without installing with uvx pun. See the installation docs for pipx and from-source options.
Verify the installation
The package root is importable after installation:
>>> from pun import __doc__
>>> isinstance(__doc__, str)
True
Usage
CLI
pun version
pun info
TUI
pun interactive
An interactive terminal user interface displays project information. Press 'q' to exit.
Support ❤️
If you have any questions or need help, feel free to open an issue on the GitHub repository.
Motivation
Features
- CLI Application: Command-line interface built with Typer
- TUI Application: Terminal user interface built with Textual
- Configuration Management: Type-safe settings using Pydantic
About
Author 🫅
This project is maintained by Hasan Sezer Taşan, It's me 👋
Analysis
- Snyk Python Package Health Analysis
- Libraries.io - PyPI
- Safety DB
- PePy Download Stats
- PyPI Download Stats
- Pip Trends Download Stats
- PyPI Map Dependency Graph
Contributing ❤️
Any contributions are welcome! Please follow the Contributing Guidelines to contribute to this project.
Development 🧰
See the Contributing Guidelines for local setup, the common development tasks (exposed via mise), building and previewing the documentation, and the VS Code debugging configurations.
Releasing
Versioning and releases are automated with release-please, driven by Conventional Commit PR titles squash-merged into main. release-please maintains a release PR that bumps the version and CHANGELOG.md; merging it tags the release and publishes to PyPI. See the Contributing Guidelines for the commit conventions, and the Repository setup guide for one-time configuration and optional post-launch integrations such as a social preview, downstream packaging, and Repology.
Pause merges that change .github/workflows/, including Renovate action-pin updates, from merging a release PR until the entire Release run finishes. Workflow differences between the release commit and current main can block tag or release creation with a 403 when using GITHUB_TOKEN. See Release recovery for prevention and recovery steps.
For adoption or template-update reconciliation, ask your agent to "audit this
template adoption/update against our existing project behavior".
The shipped template-adoption skill
also supports audits after an update was applied. It compares workflow behavior,
required checks, custom tooling, and documentation, and asks before consequential
cleanup. Its prek-workflow example shows why duplicate commands alone do not
justify removing a workflow. Use the sibling repo-setup skill for repository
settings and release setup.
Credits
This package was created with Copier and the hasansezertasan/copier-pyproject project template.
License 📜
This project is licensed under the MIT License.
Changelog 📝
For a detailed list of changes, please refer to the CHANGELOG.
Metadata
Release files for pun 0.1.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| pun-0.1.1.tar.gz | 43.6 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| pun-0.1.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 64.0 kB
Release files / pun-0.1.1.tar.gz
| Download URL | pun-0.1.1.tar.gz |
|---|---|
| Size | 43.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
08e20ce1a14d881cf33f2dc12a6bd93b4fcd8895bbeabacaa2309a547295064a
|
|
BLAKE2b-256 checksum How to use checksums |
78a1cb79376532ad38ef66d89de027ba4f2c083ada3358e62303b97221952ca4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 18, 2026.
Transparency logRelease files / pun-0.1.1-py3-none-any.whl
| Download URL | pun-0.1.1-py3-none-any.whl |
|---|---|
| Size | 20.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
83025e61ca97f159a3dc2edb98d5f9d2d2dc8921e856aa898db2cc098d11e89a
|
|
BLAKE2b-256 checksum How to use checksums |
a9b2f53816a0ef458c23220286d98d5119f203a7490cd6f0b9ee0604bc485ec6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 18, 2026.
Transparency logSecurity for pun 0.1.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for pun-0.1.1.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 18, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.