silica-scope
Interactive terminal reader for a finished SILICA AArch64 decode sweep.
SILICA decodes all 2³² AArch64
encodings through Capstone, LLVM, Unicorn and ARM's own XML spec and writes
the result to artifacts/. silica-scope reads those published artifacts
and lets you walk them: per-tool agreement, a heat map of the 256-shard
encoding space, the disagreement corpus, and the filing-ready reproducers.
It never runs a sweep. Pure Python, no native dependencies — reading a finished sweep is all it does.
Install
pipx install silica-scope
Run
silica-scope # finds the nearest artifacts/ from $PWD
silica-scope /path/to/silica/artifacts
SILICA_ARTIFACTS=/path/to/artifacts silica-scope
silica-scope --report # static summary, no TUI
Panes
| key | pane | what's in it |
|---|---|---|
1 |
overview | headline counts, per-tool agreement, taxonomy, provenance, what's on disk |
2 |
map | the 2³² space as a 16×16 shard grid, four colour channels |
3 |
corpus | stream disagreements/*.zst, filter by category, inspect any word |
4 |
reproducers | the filing-ready writeups, parsed and cross-checked |
? for the full keymap, / to look up any 32-bit encoding, r to reload
from disk, q to quit.
The map's row is a shard id's high nibble and its column the low nibble, so
shard 0xab sits at row a, column b, covering 0xab000000..0xabffffff.
Press m to cycle the colour channel; x computes exact
popcount(tool XOR spec) per shard straight off bitmaps/ when those are
present (it reads 4 × 512 MiB, so it's opt-in).
Partial artifacts
A published SILICA checkout ships only artifacts/reproducers/ and
artifacts/result_hash.txt — the bitmaps, shard records and corpus are
multi-gigabyte and regenerated locally. silica-scope treats that as a normal
state, not an error: panes that have no data say what's missing and where it
looked, and the overview never claims a sweep it can't see evidence of. A file
that exists but is malformed is reported, per pane and in a problems banner.
Source
Source, issues and the full SILICA sweep engine live at
github.com/nluevano/silica — see
tui/README.md there for building from a checkout.
Apache-2.0.
1 maintainer
Metadata
1 maintainer
Release files for silica-scope 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 |
|---|---|---|---|---|
| silica_scope-0.1.0.tar.gz | 48.0 kB | With provenance | Details for silica_scope-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| silica_scope-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for silica_scope-0.1.0-py3-none-any.whl |
Total release size: 95.0 kB
Release files / silica_scope-0.1.0.tar.gz
| Download URL | silica_scope-0.1.0.tar.gz |
|---|---|
| Size | 48.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
15f40aaf408ec3711f784226b6637f6c71d98d5ba09cee13fb6690afe42ffdc8
|
|
BLAKE2b-256 checksum How to use checksums |
21b6e6a8cacaa2f24a1fae66659841f6ee6c493aabbd243782359c3a19bdbcfc
|
| 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 Sep 1, 2026.
Transparency logRelease files / silica_scope-0.1.0-py3-none-any.whl
| Download URL | silica_scope-0.1.0-py3-none-any.whl |
|---|---|
| Size | 47.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
ba8d1d965087baffddbf769a335e962623d0039a9b44b6165fe158f89fdc6a72
|
|
BLAKE2b-256 checksum How to use checksums |
2b504b3a16540b7148fa051ba2f620b80310be2c512e4d07a7ceda6ec1c7087f
|
| 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 Sep 1, 2026.
Transparency logSecurity for silica-scope 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 silica_scope-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 Sep 1, 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.
