Relic Tool - UCS
Disclaimer
Not affiliated with Sega, Relic Entertainment, or THQ.
Description
A library for reading / writing Relic's UCS (Language) files.
Installation (Pip)
Installing from PyPI (Recommended)
pip install relic-tool-ucs
Installing from GitHub
For more information, see pip VCS support
pip install git+https://github.com/MAK-Relic-Tool/Relic-Tool-UCS
1 maintainer
Metadata
1 maintainer
Release files for relic-tool-ucs 1.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 | |
|---|---|---|---|---|
| relic_tool_ucs-1.1.0.tar.gz | 19.2 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| relic_tool_ucs-1.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 36.9 kB
Release files / relic_tool_ucs-1.1.0.tar.gz
| Download URL | relic_tool_ucs-1.1.0.tar.gz |
|---|---|
| Size | 19.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
850fe23a5e6829c1a9d707e9b69a7085dafe1aeec648f91a349ad5743a8b7126
|
|
BLAKE2b-256 checksum How to use checksums |
48cc44c71357db77f5e9a44073e54a638f1918fe47712e16dd63f3c7f5e2ceae
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
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 Mar 10, 2025.
Transparency logRelease files / relic_tool_ucs-1.1.0-py3-none-any.whl
| Download URL | relic_tool_ucs-1.1.0-py3-none-any.whl |
|---|---|
| Size | 17.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
0f357175576e6f5ad006e4a19e06018b461594a5979b9412a93ed109a775e639
|
|
BLAKE2b-256 checksum How to use checksums |
17d1a15a23c93b1837fe97a379240eeb098c4bc8a5f1122e903d83a1c7a5f81c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
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 Mar 10, 2025.
Transparency logSecurity for relic-tool-ucs 1.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
All 2 files in this release have been uploaded with provenance metadata.
Attestation for relic_tool_ucs-1.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 Mar 10, 2025.
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.
