wiswa-typing
Shared type aliases used across the Wiswa ecosystem (wiswa, wiswa-vcs, wiswa-mcp).
This package ships types only — there is no runtime code. Its surface is intentionally
small: just the two Literal aliases that more than one Wiswa package needs to agree on.
Installation
pip install wiswa-typing
Usage
from wiswa.typing import PackageManager, ProjectType
PackageManager:Literal['poetry', 'uv'].ProjectType:Literal['c', 'c++', 'generic', 'lua', 'python', 'typescript', 'xcode'].
Wiswa-internal settings shapes (Settings, PyProject, PackageJSON, VSCode, etc.) live in
wiswa under wiswa.tool.typing. GitHub and GitLab REST
payload types (Repository, Badge, RemoteSettings, ProjectSettings, etc.) live in
wiswa-vcs under wiswa.vcs.typing.
Metadata
Release files for wiswa-typing 0.1.0
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 | Actions |
|---|---|---|---|---|
| wiswa_typing-0.1.0.tar.gz | 5.3 kB | With provenance | Details for wiswa_typing-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| wiswa_typing-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for wiswa_typing-0.1.0-py3-none-any.whl |
Total release size: 9.6 kB
Release files / wiswa_typing-0.1.0.tar.gz
| Download URL | wiswa_typing-0.1.0.tar.gz |
|---|---|
| Size | 5.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
2af2ec4d566dc5e5e41fd96ed83a037ffe78c5a071446acfb00a0d88370651ab
|
|
BLAKE2b-256 checksum How to use checksums |
22d43d6903d4a0a0c9c23909459007bb4b62474b9a4ce4d75062231aef6d7456
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 May 22, 2026.
Transparency logRelease files / wiswa_typing-0.1.0-py3-none-any.whl
| Download URL | wiswa_typing-0.1.0-py3-none-any.whl |
|---|---|
| Size | 4.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
f69fffdb42e1255c1c66c6a515606774e19b4a8bafe10672b71c34b549968a69
|
|
BLAKE2b-256 checksum How to use checksums |
44f17272498a674a05abc518a2873c61df99d46c4d108e6e0b4aeecdc6135f65
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 May 22, 2026.
Transparency logSecurity for wiswa-typing 0.1.0
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
Both files in this release have been uploaded with provenance metadata.
Attestation for wiswa_typing-0.1.0.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 May 22, 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.