Unseal - Mechanistic Interpretability for Transformers
Prerequisites
Unseal requires python 3.6+.
Installation
For its visualizations interfaces, Unseal uses this fork of the PySvelte library, which can be installed via pip:
git clone git@github.com:TomFrederik/PySvelte.git
cd PySvelte
pip install -e .
In order to run PySvelte, you will also need to install npm via your package manager.
The hooking functionality of Unseal should still work without PySvelte, but we can't give any guarantees
Install Unseal via pip
pip install unseal
Usage
We refer to our documentation for tutorials and usage guides:
Notebooks
Here are some notebooks that also showcase Unseal's functionalities.
1 maintainer
Metadata
1 maintainer
Release files for Unseal 0.2.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 | |
|---|---|---|---|---|
| Unseal-0.2.1.tar.gz | 16.3 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| Unseal-0.2.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 39.1 kB
Release files / Unseal-0.2.1.tar.gz
| Download URL | Unseal-0.2.1.tar.gz |
|---|---|
| Size | 16.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
5dadb5201621cf1dbd4817eb435276cb804a5e8cb0960f758443809379810206
|
|
BLAKE2b-256 checksum How to use checksums |
30b1d79725fc40fd54626f915510d7df4aa5ab5a20517317b28db1b3a42dafa3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.8.0 pkginfo/1.8.2 readme-renderer/34.0 requests/2.27.1 requests-toolbelt/0.9.1 urllib3/1.26.8 tqdm/4.62.3 importlib-metadata/4.8.2 keyring/23.5.0 rfc3986/2.0.0 colorama/0.4.4 CPython/3.9.6
|
Release files / Unseal-0.2.1-py3-none-any.whl
| Download URL | Unseal-0.2.1-py3-none-any.whl |
|---|---|
| Size | 22.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
156d0781e3a6b97a989c556597d9c15203a5f55557ad273db4bdafdd0220a938
|
|
BLAKE2b-256 checksum How to use checksums |
aca18673f782cbbf3e4b5fbf813f428683af99f591917651e6c31a54cb03237a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.8.0 pkginfo/1.8.2 readme-renderer/34.0 requests/2.27.1 requests-toolbelt/0.9.1 urllib3/1.26.8 tqdm/4.62.3 importlib-metadata/4.8.2 keyring/23.5.0 rfc3986/2.0.0 colorama/0.4.4 CPython/3.9.6
|
Security for Unseal 0.2.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.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A 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.
