Sericite
Sericite is a scripting language and its execution engine, built around a single idea: creating a fully isolated, arbitrarily nestable runtime environment should be a cheap, first-class operation in the language itself.
Syntax borrows a subset of Python, but Sericite source is compiled into Sericite's own instruction stream and executed by the Sericite engine — never through exec/eval. Every VM starts with zero capabilities: its own virtual IO, its own in-memory filesystem, and the ability to create child VMs. Everything else (network, host data, whatever you choose) is granted explicitly, layer by layer, through FFI.
Status
0.3.0 prototype. The engine is a Python reference implementation (codename Sericite-PY): zero runtime dependencies, Python ≥ 3.12, 221 regression tests. APIs and semantics may change before 1.0.
Security note. Sericite is designed for isolation, but the current prototype runs in the host process and has not been formally audited. Do not rely on it as the only boundary when executing adversarial code. See the security model for exactly what is and is not guaranteed.
Install
pip install sericite
The distribution is named sericite; the import package is sericite.
Quick start
As a CLI:
printf 'print("hello from sericite")\n' > hello.sericite
sericite hello.sericite # hello from sericite
Embedded in Python:
from sericite import SericiteEngine
engine = SericiteEngine()
vm = engine.create_root("""
sub = VM("print('hello from a child VM')")
print(sub.run())
""")
print(vm.run(), end="")
Grant a capability to a VM (FFI):
def double(x):
return x * 2
vm = engine.create_root("print(double(21))", functions={"double": double})
print(vm.run(), end="") # 42
What a Sericite VM is
A VM is a cheap, self-contained workspace:
- it cannot see its parent's variables, files, or handles, and cannot tell how deep it is nested;
- it has its own empty in-memory filesystem (text only — structurally unable to touch the real disk);
- resource quotas (instructions, memory, output, child VMs, nesting depth, …) can only be tightened, never loosened, and a child's consumption is charged to all its ancestors;
- its parent can preset files, feed input, single-step it statement by statement or instruction by instruction, snapshot its state, or terminate it;
- it can create its own child VMs — isolation is recursive, because untrusted code is.
Cheap is measured, not just claimed: in the current Python prototype, creating a child VM from inside a script costs ~0.05 ms — the same order as spawning a thread, one to two orders of magnitude below a process. A representative loop averages ~0.65 µs per instruction, or ~1.86 µs per instruction with instruction-level stepping (environment and reproduction scripts: benchmarks/).
Documentation
| Document | Language | Contents |
|---|---|---|
| Design notes | EN | What Sericite is, why it exists, where the boundaries are (中文) |
| Prior art | EN | Safe-Tcl and related work: what Sericite inherits, what it adds (中文) |
| Language reference | EN | The language subset and semantics, self-contained (中文) |
| Architecture | EN | Engine structure, invariants, resource quotas (中文) |
| Security model | EN | Threat model; what the engine does and does not guarantee (中文) |
| Build journal | EN index | How Sericite 0.1.0 was built, stage by stage, with runnable checkpoints (git checkout stage-1 … stage-6); articles in 中文 |
| Behind the scenes | EN index | Origin story and how AI-assisted development was used; articles in 中文 |
The build-journal and behind-the-scenes articles are Chinese-only (their index pages have English versions); full translations are not planned — they are frozen history.
How this project was built
Sericite was developed with AI assistance throughout — design discussion, implementation, testing, adversarial review, and documentation drafting. What the AI did, what the author did, and how outputs were verified are documented in AI-assisted development (中文), with selected conversation records alongside.
Roadmap
- List/dict/string methods and more ergonomic syntax
- Performance benchmarks: VM creation, per-instruction execution, and debugging costs measured (see benchmarks/); broader workload coverage still pending
- A normative language spec and a conformance test suite, so a future non-Python engine can be validated against them
- Evaluation of a native engine (the package name is language-level on purpose:
sericitesurvives an engine rewrite)
The name
Sericite (绢云母) is the finest-grained member of the mica family: thin silky scales that stack into sheets, and an insulator like every mica. The name keeps the three promises the project is named after — layering, insulation, lightness.
(The project was briefly named Mica/MicaLang; it was renamed after discovering the name was occupied multiple times over, including an actively developed commercial language publishing Docker images under the micalang namespace.)
License
Apache-2.0 — see NOTICE.
Metadata
Release files for sericite 0.3.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 | |
|---|---|---|---|---|
| sericite-0.3.0.tar.gz | 173.6 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| sericite-0.3.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 203.6 kB
Release files / sericite-0.3.0.tar.gz
| Download URL | sericite-0.3.0.tar.gz |
|---|---|
| Size | 173.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
1dad516a17b77ab82fb8b64e22d08d95b7aaecb1ceaa577ae50eae353610daf3
|
|
BLAKE2b-256 checksum How to use checksums |
09b5bd209ee9b77e91b873ee7276ada67285e045962593f2f938901809937bd8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 23, 2026.
Transparency logRelease files / sericite-0.3.0-py3-none-any.whl
| Download URL | sericite-0.3.0-py3-none-any.whl |
|---|---|
| Size | 30.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
e36fd7f9ff9fd07fec73877e6752610d8d740b2bb328baa7a63a077ae5bf13ab
|
|
BLAKE2b-256 checksum How to use checksums |
ecfd5b1ed816964295cd197d452ba906dceac0081abb4516bf5ef6dd7ce7c4eb
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 23, 2026.
Transparency logSecurity for sericite 0.3.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 sericite-0.3.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 Oct 23, 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.