oscilo
Zero-invasive variable-change tracker for Python. Register a variable once and oscilo records every change it undergoes — without touching your code.
English | 한국어
oscilo observes program execution in the background and captures how a variable evolves over time — reassignments, in-place mutations, and deletions — then writes the full history to a JSON Lines file when the program exits. The value comparison that runs on every line is delegated to a small C extension to keep the runtime overhead low.
Contents
- Motivation
- Installation
- Quick start
- Output format
- How it works
- Project layout
- Testing
- Contributing
- License
Motivation
Inspecting variable state during debugging usually means scattering print calls through the code:
def solve(data):
result = []
for x in data:
result.append(x * 2)
print("result:", result) # temporary, easy to forget to remove
return result
This clutters the source, is easy to leave behind, and does not scale to hot loops. Interactive debuggers avoid the clutter but interrupt execution, which is impractical when a loop runs thousands of times.
oscilo takes a different approach: register a variable by name once, and its history is collected automatically.
import oscilo
def solve(data):
result = []
oscilo.register("result") # every change to `result` from here on is recorded
for x in data:
result.append(x * 2)
return result
Installation
pip install oscilo
oscilo ships a C extension. A prebuilt wheel is used when available; otherwise the extension is compiled locally, which requires a C compiler.
Building from source
pip install -e . # editable install (recommended for development)
pip install . # standard install
python setup.py build_ext --inplace # build the C extension only
Requirements
- Python 3.11+
- A C compiler (GCC / Clang / MSVC) when building from source
Quick start
The public API is a single function, oscilo.register(), which takes the variable name as a string.
import oscilo
def run():
target = [100, 200]
oscilo.register("target") # recorded as an "init" event
target.append(300) # updated (in-place mutation)
target = "reassigned" # updated (reassignment)
del target # deleted
run()
# On exit, the history is written to oscilo.jsonl
Calling oscilo.register() multiple times adds each variable to the same monitor, and all histories are merged into a single output file:
import oscilo
def run():
score = 10
items = ["potion", "shield"]
oscilo.register("score")
oscilo.register("items")
score += 55
items.append("sword")
run()
Notes:
register()returnsNone; registration is its only effect.- Importing
oscilohas no side effects — tracing starts only whenregister()is called. - If no change is ever recorded, no file is written.
Output format
History is written as JSON Lines (oscilo.jsonl by default). Each line represents a single change:
{"name": "target", "var_id": 1, "data": [100, 200], "event": "init", "domain": "LOCAL", "line": 4, "func": "run", "call_id": 1, "parent_call_id": null, "call_depth": 1}
{"name": "target", "var_id": 1, "data": [100, 200, 300], "event": "updated", "domain": "LOCAL", "line": 6, "func": "run", "call_id": 1, "parent_call_id": null, "call_depth": 1}
{"name": "target", "var_id": 1, "data": "reassigned", "event": "updated", "domain": "LOCAL", "line": 7, "func": "run", "call_id": 1, "parent_call_id": null, "call_depth": 1}
{"name": "target", "var_id": 1, "data": null, "event": "deleted", "domain": "LOCAL", "line": 8, "func": "run", "call_id": 1, "parent_call_id": null, "call_depth": 1}
| Field | Description |
|---|---|
name |
The tracked variable name |
var_id |
Identity of the tracked binding; records sharing a var_id refer to the same variable (matches call_id for locals; stays stable across frames for globals and closure variables) |
data |
The value at the time of the change (null for deleted) |
event |
init, updated, or deleted |
domain |
Variable scope: LOCAL or GLOBAL (a closure/enclosing variable is reported as LOCAL from its owning frame's point of view and is identified by var_id) |
line |
Source line where the change was detected |
func |
Function in which the change occurred (<module> at module level) |
call_id |
Unique id of the function call (frame) where the change occurred |
parent_call_id |
call_id of the calling frame (null for a root call) |
call_depth |
Call depth relative to the registration frame (root = 1) |
The call_id / parent_call_id / call_depth fields let a consumer reconstruct the call tree — i.e. which call each change happened in, and how the calls nest.
The line-delimited format streams and parses efficiently for large histories.
How it works
oscilo watches execution in Python and delegates value comparison to a C extension.
-
The first
register()call lazily creates a single monitor and installs a trace hook viasys.settrace. -
On each executed line, the C engine (
oscilo_engine) determines whether a tracked variable changed, using a short-circuiting sequence:Variable no longer in scope? → deleted Reference identity changed? → updated (reassignment) Immutable type (int/str/...)? → unchanged (skip comparison) Container size changed? → updated Otherwise, compare values → updated / unchanged -
When the process exits, an
atexithook flushes the in-memory history to disk in a single write. Records are buffered rather than written per change to avoid I/O overhead.
Unchanged values produce no record, and immutable values are skipped entirely when their reference is unchanged — both are central to keeping the per-line cost low.
Project layout
src/oscilo/
├── __init__.py # public API (register) and single-instance management
├── _core.py # monitor implementation and atexit save logic
├── CallContext.py # lazy call-context tracking (call_id / parent_call_id / call_depth)
├── FileWriter.py # JSONL output
├── HistoryBuffer.py # in-memory history buffer
├── ScopeResolver.py # LEGB scope resolution (local/enclosing/global/builtin)
├── TraceDispatcher.py # sys.settrace event handling
├── VariableTracker.py # per-variable change detection and value snapshots
└── oscilo_engine.c # C extension for value comparison
Testing
python tests/test.py
Tests are discovered from tests/ (test_*.py). Component tests run in-process, while the end-to-end scenarios (registration and process lifecycle) spawn a separate interpreter process, since atexit-driven saving and sys.settrace behavior can only be verified across a full process lifetime.
Contributing
Contributions are welcome — bug reports, feature ideas, and pull requests alike.
- Open an issue using the bug report or feature request template.
- Follow the checklist in
.github/pull_request_template.mdwhen submitting a PR. - Include tests with new features or fixes where practical.
License
1 maintainer
Metadata
1 maintainer
Release files for oscilo 1.0.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 | |
|---|---|---|---|---|
| oscilo-1.0.1.tar.gz | 219.1 kB | With provenance | Details |
Built distributions (wheels)
Total release size: 801.5 kB
Release files / oscilo-1.0.1.tar.gz
| Download URL | oscilo-1.0.1.tar.gz |
|---|---|
| Size | 219.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e7a4d7ac1af354c3e625eb9919892c56752434ad7d3d77f9423cac693e25a490
|
|
BLAKE2b-256 checksum How to use checksums |
3cd4708c930de80f23b8b87fd3b923e77c8b4ed0812f37fc4d79d1d97183afb2
|
| 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 Aug 1, 2026.
Transparency logRelease files / oscilo-1.0.1-cp313-cp313-win_amd64.whl
| Download URL | oscilo-1.0.1-cp313-cp313-win_amd64.whl |
|---|---|
| Size | 24.2 kB |
| Tags | CPython 3.13 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
7343b71958be5c539070b9459c34502c75a4044c09fa14d36909bf97a8efa786
|
|
BLAKE2b-256 checksum How to use checksums |
95f31625adce4662a303eca15ba086c8cd0ac9a4ecbb29429e361cd63e52b464
|
| 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 Aug 1, 2026.
Transparency logRelease files / oscilo-1.0.1-cp313-cp313-win32.whl
| Download URL | oscilo-1.0.1-cp313-cp313-win32.whl |
|---|---|
| Size | 24.0 kB |
| Tags | CPython 3.13 Windows x86-32 |
|
SHA-256 checksum How to use checksums |
08fd4b31240bf6c2efc52a3cca53c31061220d02e1fbd5c00f430100be46a95c
|
|
BLAKE2b-256 checksum How to use checksums |
0a98517820227f15f16def19eef593b5e9de201c679c67307cc340babfb4fdc1
|
| 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 Aug 1, 2026.
Transparency logRelease files / oscilo-1.0.1-cp313-cp313-musllinux_1_2_x86_64.whl
| Download URL | oscilo-1.0.1-cp313-cp313-musllinux_1_2_x86_64.whl |
|---|---|
| Size | 31.0 kB |
| Tags | CPython 3.13 Linux musl 1.2+ x86-64 |
|
SHA-256 checksum How to use checksums |
63ad0c45d4e5972d1459ea75618df0ef15fe1e9bef735123b815867e9903a33d
|
|
BLAKE2b-256 checksum How to use checksums |
2097a994a4617d737297aac8a8eb643d3d76fb1c5cbbabf0981c9d2af4b867ae
|
| 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 Aug 1, 2026.
Transparency logRelease files / oscilo-1.0.1-cp313-cp313-musllinux_1_2_i686.whl
| Download URL | oscilo-1.0.1-cp313-cp313-musllinux_1_2_i686.whl |
|---|---|
| Size | 31.0 kB |
| Tags | CPython 3.13 Linux musl 1.2+ x86-32 |
|
SHA-256 checksum How to use checksums |
101ae208708be62473652887dc674db9d54d4ad4a99d1ffe3d19b477d7917a2c
|
|
BLAKE2b-256 checksum How to use checksums |
84934a3df920e5e3ec00eaf47aea44b62923dc0416e4c6f2af624fca75760e6d
|
| 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 Aug 1, 2026.
Transparency logRelease files / oscilo-1.0.1-cp313-cp313-manylinux_2_5_x86_64.manylinux1_x86_64.manylinux_2_17_x86_64.manylinux2014_x86_64.whl
| Download URL | oscilo-1.0.1-cp313-cp313-manylinux_2_5_x86_64.manylinux1_x86_64.manylinux_2_17_x86_64.manylinux2014_x86_64.whl |
|---|---|
| Size | 31.1 kB |
| Tags | CPython 3.13 Linux glibc 2.17+ x86-64 Linux glibc 2.5+ x86-64 |
|
SHA-256 checksum How to use checksums |
07cc82d53568d26a6bef1c401562a1be96f2098d257dc65de9159b3f10263517
|
|
BLAKE2b-256 checksum How to use checksums |
e0f25b983e913656849b8bf4fc8ee961f5ed0ed1936b0fbf15ab30b7153a3da6
|
| 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 Aug 1, 2026.
Transparency logRelease files / oscilo-1.0.1-cp313-cp313-manylinux_2_5_i686.manylinux1_i686.manylinux_2_17_i686.manylinux2014_i686.whl
| Download URL | oscilo-1.0.1-cp313-cp313-manylinux_2_5_i686.manylinux1_i686.manylinux_2_17_i686.manylinux2014_i686.whl |
|---|---|
| Size | 30.8 kB |
| Tags | CPython 3.13 Linux glibc 2.17+ x86-32 Linux glibc 2.5+ x86-32 |
|
SHA-256 checksum How to use checksums |
fc0d6efcbb0b622775721592ee41f2a56a79aa3068f9be081eabae33a9252563
|
|
BLAKE2b-256 checksum How to use checksums |
df4953bb3cadfb1853d55990e8ea214d092cb7b16ac276d9a4e0f29bd93bffe1
|
| 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 Aug 1, 2026.
Transparency logRelease files / oscilo-1.0.1-cp313-cp313-macosx_11_0_arm64.whl
| Download URL | oscilo-1.0.1-cp313-cp313-macosx_11_0_arm64.whl |
|---|---|
| Size | 22.0 kB |
| Tags | CPython 3.13 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
99d1966cc877438bbb6c44f0a3d04728c2215f59287b0ee715a0ffb20f84127b
|
|
BLAKE2b-256 checksum How to use checksums |
f731ec2643caa374768008fd4c085f7077eaa199093dab6d7306966d1cdbfb2b
|
| 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 Aug 1, 2026.
Transparency logRelease files / oscilo-1.0.1-cp312-cp312-win_amd64.whl
| Download URL | oscilo-1.0.1-cp312-cp312-win_amd64.whl |
|---|---|
| Size | 24.2 kB |
| Tags | CPython 3.12 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
17220e37773721b0854d3c2bbb4035c218aa7e4835b8614cb058902aee11abec
|
|
BLAKE2b-256 checksum How to use checksums |
d35f74d19c60803402707e89e7963ad782eb4175709a50f34b32d7e406b9c91e
|
| 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 Aug 1, 2026.
Transparency logRelease files / oscilo-1.0.1-cp312-cp312-win32.whl
| Download URL | oscilo-1.0.1-cp312-cp312-win32.whl |
|---|---|
| Size | 24.0 kB |
| Tags | CPython 3.12 Windows x86-32 |
|
SHA-256 checksum How to use checksums |
cce63d24690574fbfec0cf856de9288faf33370532bec04b861d258a7e727e84
|
|
BLAKE2b-256 checksum How to use checksums |
49bafd5aeec0407d13ed7d8169d09806b6d2f6ab8ce432cc9ab10d07486fe4ac
|
| 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 Aug 1, 2026.
Transparency logRelease files / oscilo-1.0.1-cp312-cp312-musllinux_1_2_x86_64.whl
| Download URL | oscilo-1.0.1-cp312-cp312-musllinux_1_2_x86_64.whl |
|---|---|
| Size | 31.2 kB |
| Tags | CPython 3.12 Linux musl 1.2+ x86-64 |
|
SHA-256 checksum How to use checksums |
d5d810a9ebe47e3d5c04ab2404c99b614032931f234c2f95bc1ddb8c5a6fe800
|
|
BLAKE2b-256 checksum How to use checksums |
c091f24bc3534380541d09cc427b5fafaa2ccd175023cc253003cb5946a5b73e
|
| 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 Aug 1, 2026.
Transparency logRelease files / oscilo-1.0.1-cp312-cp312-musllinux_1_2_i686.whl
| Download URL | oscilo-1.0.1-cp312-cp312-musllinux_1_2_i686.whl |
|---|---|
| Size | 31.2 kB |
| Tags | CPython 3.12 Linux musl 1.2+ x86-32 |
|
SHA-256 checksum How to use checksums |
49144fc23ba32ad820c57de4c688a34b8d1cdc8c197d1d1f70844bc4f7c94bf0
|
|
BLAKE2b-256 checksum How to use checksums |
31c3f1cb9cf5ee9b71ac95bf5e3a0e91adba8bd0db59122e67e09fc12efa3238
|
| 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 Aug 1, 2026.
Transparency logRelease files / oscilo-1.0.1-cp312-cp312-manylinux_2_5_x86_64.manylinux1_x86_64.manylinux_2_17_x86_64.manylinux2014_x86_64.whl
| Download URL | oscilo-1.0.1-cp312-cp312-manylinux_2_5_x86_64.manylinux1_x86_64.manylinux_2_17_x86_64.manylinux2014_x86_64.whl |
|---|---|
| Size | 31.4 kB |
| Tags | CPython 3.12 Linux glibc 2.17+ x86-64 Linux glibc 2.5+ x86-64 |
|
SHA-256 checksum How to use checksums |
81c27c2e0cb74567b68032a29404bb7803a86e5c80fd2e3987ac3b8d73f42611
|
|
BLAKE2b-256 checksum How to use checksums |
8a582eba0552c1496c1faf71e7fb948c7586d601e6fed671129fa14c4a964120
|
| 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 Aug 1, 2026.
Transparency logRelease files / oscilo-1.0.1-cp312-cp312-manylinux_2_5_i686.manylinux1_i686.manylinux_2_17_i686.manylinux2014_i686.whl
| Download URL | oscilo-1.0.1-cp312-cp312-manylinux_2_5_i686.manylinux1_i686.manylinux_2_17_i686.manylinux2014_i686.whl |
|---|---|
| Size | 30.9 kB |
| Tags | CPython 3.12 Linux glibc 2.17+ x86-32 Linux glibc 2.5+ x86-32 |
|
SHA-256 checksum How to use checksums |
b98cf2df968f8b937dba92d895211eebc11e251762e903cc5c0bcb4d8635e8a7
|
|
BLAKE2b-256 checksum How to use checksums |
0a06effd3bb4cb6a6977fd74193cfcdab09e9d420147fb51e9860e55843840ae
|
| 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 Aug 1, 2026.
Transparency logRelease files / oscilo-1.0.1-cp312-cp312-macosx_11_0_arm64.whl
| Download URL | oscilo-1.0.1-cp312-cp312-macosx_11_0_arm64.whl |
|---|---|
| Size | 22.0 kB |
| Tags | CPython 3.12 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
2e1b07294134dfede79f068bbea50d825034348c855a99f604d7cad0235869ed
|
|
BLAKE2b-256 checksum How to use checksums |
afb037a8807853a58e1d2158a745d5a286ccbe34b2fbc54c45fa6ae86e9ccfeb
|
| 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 Aug 1, 2026.
Transparency logRelease files / oscilo-1.0.1-cp311-cp311-win_amd64.whl
| Download URL | oscilo-1.0.1-cp311-cp311-win_amd64.whl |
|---|---|
| Size | 24.2 kB |
| Tags | CPython 3.11 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
8672daa0af4cd4b2a7f60405c69f2f6945ab5663a9c2b84b97089fe4bb19cf55
|
|
BLAKE2b-256 checksum How to use checksums |
0da1ce5c8f034bab5ccdd801d2a34ca33ebdc5aa997473d0fd725a58cfd1faba
|
| 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 Aug 1, 2026.
Transparency logRelease files / oscilo-1.0.1-cp311-cp311-win32.whl
| Download URL | oscilo-1.0.1-cp311-cp311-win32.whl |
|---|---|
| Size | 24.0 kB |
| Tags | CPython 3.11 Windows x86-32 |
|
SHA-256 checksum How to use checksums |
7cc29e48581187acb187c9f373e6d5575f029e984ee469d9a887b75c70674e9f
|
|
BLAKE2b-256 checksum How to use checksums |
120ed99eb4af1be07d7dc5d41bdeb819cf4c432fb48c56586aecba66699cf304
|
| 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 Aug 1, 2026.
Transparency logRelease files / oscilo-1.0.1-cp311-cp311-musllinux_1_2_x86_64.whl
| Download URL | oscilo-1.0.1-cp311-cp311-musllinux_1_2_x86_64.whl |
|---|---|
| Size | 30.8 kB |
| Tags | CPython 3.11 Linux musl 1.2+ x86-64 |
|
SHA-256 checksum How to use checksums |
2b7c4355398dd9214d8c245e663786d8bd45a9332e0837d75c83540bcda9bf1e
|
|
BLAKE2b-256 checksum How to use checksums |
6958b3a2e025c72b262d3056d3195ef570fd1e58b7985c109e0094ef69718791
|
| 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 Aug 1, 2026.
Transparency logRelease files / oscilo-1.0.1-cp311-cp311-musllinux_1_2_i686.whl
| Download URL | oscilo-1.0.1-cp311-cp311-musllinux_1_2_i686.whl |
|---|---|
| Size | 30.8 kB |
| Tags | CPython 3.11 Linux musl 1.2+ x86-32 |
|
SHA-256 checksum How to use checksums |
62ae2539ac41b0bc85cbcd6baf1bf574cd4bd2e0a96a7fbf743153c6dd2eceab
|
|
BLAKE2b-256 checksum How to use checksums |
431028413961b5310f4b58533380da6c65d7ad270dc5ec93ef9472c1c2df8313
|
| 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 Aug 1, 2026.
Transparency logRelease files / oscilo-1.0.1-cp311-cp311-manylinux_2_5_x86_64.manylinux1_x86_64.manylinux_2_17_x86_64.manylinux2014_x86_64.whl
| Download URL | oscilo-1.0.1-cp311-cp311-manylinux_2_5_x86_64.manylinux1_x86_64.manylinux_2_17_x86_64.manylinux2014_x86_64.whl |
|---|---|
| Size | 30.9 kB |
| Tags | CPython 3.11 Linux glibc 2.17+ x86-64 Linux glibc 2.5+ x86-64 |
|
SHA-256 checksum How to use checksums |
ba8c66922448dfefb6baf1af5942a9d075b1f3626db08f6d745774769ec9872e
|
|
BLAKE2b-256 checksum How to use checksums |
d22f3406a688acc461045347402f0655318f4a2ca57f8a1089dcb1f43edfd338
|
| 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 Aug 1, 2026.
Transparency logRelease files / oscilo-1.0.1-cp311-cp311-manylinux_2_5_i686.manylinux1_i686.manylinux_2_17_i686.manylinux2014_i686.whl
| Download URL | oscilo-1.0.1-cp311-cp311-manylinux_2_5_i686.manylinux1_i686.manylinux_2_17_i686.manylinux2014_i686.whl |
|---|---|
| Size | 30.7 kB |
| Tags | CPython 3.11 Linux glibc 2.17+ x86-32 Linux glibc 2.5+ x86-32 |
|
SHA-256 checksum How to use checksums |
8348a7e8c3209e5268d4a915773438f00a7134f97caae4202178ffd86780f79a
|
|
BLAKE2b-256 checksum How to use checksums |
4c2c2a31ddc391a92be589713290282fe56c552bf5313d193fa1f2c5ceafec8d
|
| 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 Aug 1, 2026.
Transparency logRelease files / oscilo-1.0.1-cp311-cp311-macosx_11_0_arm64.whl
| Download URL | oscilo-1.0.1-cp311-cp311-macosx_11_0_arm64.whl |
|---|---|
| Size | 22.0 kB |
| Tags | CPython 3.11 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
6eda2d0baa6f3d04208562d0b32113beeff6524c2121ee9e7680f9e6499c2152
|
|
BLAKE2b-256 checksum How to use checksums |
9bc45cf1398285627e4691e33b0a55baea6ccd6f9d9ff49dde9061d6d2cd5995
|
| 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 Aug 1, 2026.
Transparency logSecurity for oscilo 1.0.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.
Full provenance
All 22 files in this release have been uploaded with provenance metadata.
Attestation for oscilo-1.0.1.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 Aug 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.
