Skip to main content
T1C-IR Logo

T1C-IR - Intermediate Representation for T1C Neuromorphic Hardware

T1C-IR is an intermediate representation designed for Type 1 Compute (T1C) neuromorphic hardware. It provides a standardized format for representing spiking neural networks with support for serialization, graph manipulation, and hardware-specific optimizations.

T1C-IR serves as an intermediate format between neuromorphic frameworks and hardware platforms, enabling seamless model portability and deployment.

Read more about T1C-IR in our documentation

Installation

uv add t1c-ir@git@github.com:type1compute/t1cir.git

Or with pip:

pip install t1c-ir

Usage

T1C-IR serves as a format between neuromorphic platforms and will be installed alongside your framework of choice. Using T1C-IR follows a simple pattern when you want to move from a source to a target platform:

from t1c.ir import read, write

# Define a model
my_model = ...
# Save the model (source platform)
write("my_graph.t1c", my_model)
# Load the model (target platform)
imported_graph = read("my_graph.t1c")

Quick Start

from t1c.ir import Graph, Input, Output, Affine, LIF, read, write
import numpy as np

# Create a simple network
nodes = {
    "input": Input(input_type={"input": np.array([784])}),
    "fc1": Affine(
        weight=np.random.randn(128, 784).astype(np.float32),
        bias=np.zeros(128, np.float32)
    ),
    "lif1": LIF(
        tau=np.ones(128, np.float32) * 10.0,
        r=np.ones(128, np.float32) * 10.0,
        v_leak=np.zeros(128, np.float32),
        v_threshold=np.ones(128, np.float32)
    ),
    "output": Output(output_type={"output": np.array([128])})
}
edges = [("input", "fc1"), ("fc1", "lif1"), ("lif1", "output")]
graph = Graph(nodes=nodes, edges=edges)

# Serialize to file
write("model.t1c", graph)

# Load from file
loaded = read("model.t1c")

See our example section for a complete pipeline from snnTorch to T1C hardware.

Frameworks that currently support T1C-IR

Framework Write to T1C-IR Read from T1C-IR Examples
snnTorch ✓ ✓ snnTorch to T1C tutorial

Primitives

T1C-IR supports the following computational primitives:

Primitive Description
Input Network input node
Output Network output node
Affine Fully-connected layer (Linear)
SpikingAffine Hardware-optimized spiking linear layer
Conv2d 2D convolution
SepConv2d Depthwise separable convolution
MaxPool2d 2D max pooling
AvgPool2d 2D average pooling
Upsample 2D spatial upsampling (nearest/bilinear)
Flatten Tensor flattening
LIF Leaky Integrate-and-Fire neuron
Skip Skip/residual connection

NIR Acknowledgement

T1C-IR is inspired by and builds upon the Neuromorphic Intermediate Representation (NIR) project, a collaborative effort to create a standardized format for neuromorphic computing across multiple platforms.

We acknowledge the NIR authors and their published work:

Pedersen, Jens E. et al. "Neuromorphic intermediate representation: A unified instruction set for interoperable brain-inspired computing." Nature Communications 15, 8122 (2024). https://doi.org/10.1038/s41467-024-52259-9

T1C-IR vs NIR: Key Differences

T1C-IR is not a fork of NIR. It is an independent implementation that shares similar design principles but is specifically tailored for Type 1 Compute (T1C) FPGA hardware. The key differences are:

Aspect NIR T1C-IR
Target Cross-platform interoperability T1C FPGA hardware
Primitives General-purpose set (17+ primitives) Hardware-focused subset
Serialization HDF5 (.nir files) HDF5 (.t1c files)
Graph structure Allows cycles (recurrent) DAG-only (temporal recurrence via state)
File format Compatible structure Similar but independent

Primitives Comparison

T1C-IR Primitive NIR Equivalent Notes
Affine Affine Same semantics (y = Wx + b)
LIF LIF Same NIR-compliant dynamics
Conv2d Conv2d Same semantics
Flatten Flatten Same semantics
MaxPool2d SumPool2d T1C-IR uses max, NIR uses sum
AvgPool2d AvgPool2d Same semantics
Upsample (none) T1C-IR addition: FPN/detection support
Skip (edge-based) T1C-IR addition: Explicit skip node
SpikingAffine (none) T1C-IR addition: Hardware hints
SepConv2d (none) T1C-IR addition: Mobile/edge efficiency
(none) Linear NIR has weight-only linear (no bias)
(none) IF, LI, I NIR has more neuron variants
(none) CubaLIF, CubaLI NIR has current-based neurons
(none) Delay NIR has explicit delay nodes
(none) Threshold NIR has standalone threshold
(none) Scale NIR has scaling operation
(none) Conv1d NIR has 1D convolution

Why T1C-IR is Separate

  1. Hardware specificity: T1C-IR includes primitives like SpikingAffine with quantization hints (weight_bits, accumulator_bits) that are specific to T1C FPGA compilation.

  2. DAG enforcement: T1C hardware benefits from directed acyclic graphs for pipelining. Temporal recurrence is handled via stateful neurons across timesteps, not graph cycles.

  3. Skip as node: T1C-IR represents skip/residual connections as explicit nodes rather than edge annotations. This provides clearer hardware mapping for T1C compilers.

  4. Focused primitive set: T1C-IR only includes primitives relevant to T1C deployment, avoiding complexity from unused neuron types.

  5. Independent evolution: T1C-IR can evolve to match T1C hardware requirements without being constrained by cross-platform compatibility.

File Format Compatibility

T1C-IR .t1c files use HDF5 with a structure similar to NIR .nir files:

├── version          # Format version string
└── node/            # Graph root
    ├── type         # "Graph"
    ├── nodes/       # Node dictionary
    │   ├── input/
    │   ├── fc1/
    │   └── ...
    └── edges/       # Edge list
        ├── src      # Source node names
        └── dst      # Destination node names

While structurally similar, T1C-IR files are not directly interchangeable with NIR files due to:

  • Different primitive type names in some cases
  • T1C-IR-specific primitives (SpikingAffine, SepConv2d, Skip)
  • Different version strings

Documentation

For more information, visit the T1C-IR documentation.

Metadata

Release files for t1c-ir 0.0.2

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Built distributions (wheels)

Table of built distributions (wheels) for t1c-ir 0.0.2
File Actions
t1c_ir-0.0.2-cp313-cp313-win_amd64.whl CPython 3.13 CPython 3.13 Windows x86-64 Details for t1c_ir-0.0.2-cp313-cp313-win_amd64.whl
t1c_ir-0.0.2-cp313-cp313-win32.whl CPython 3.13 CPython 3.13 Windows x86-32 Details for t1c_ir-0.0.2-cp313-cp313-win32.whl
t1c_ir-0.0.2-cp313-cp313-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl CPython 3.13 CPython 3.13 Linux glibc 2.17+ x86-64, Linux glibc 2.28+ x86-64 Details for t1c_ir-0.0.2-cp313-cp313-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
t1c_ir-0.0.2-cp313-cp313-macosx_11_0_arm64.whl CPython 3.13 CPython 3.13 macOS 11.0+ ARM64 Details for t1c_ir-0.0.2-cp313-cp313-macosx_11_0_arm64.whl
t1c_ir-0.0.2-cp312-cp312-win_amd64.whl CPython 3.12 CPython 3.12 Windows x86-64 Details for t1c_ir-0.0.2-cp312-cp312-win_amd64.whl
t1c_ir-0.0.2-cp312-cp312-win32.whl CPython 3.12 CPython 3.12 Windows x86-32 Details for t1c_ir-0.0.2-cp312-cp312-win32.whl
t1c_ir-0.0.2-cp312-cp312-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl CPython 3.12 CPython 3.12 Linux glibc 2.28+ x86-64, Linux glibc 2.17+ x86-64 Details for t1c_ir-0.0.2-cp312-cp312-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
t1c_ir-0.0.2-cp312-cp312-macosx_11_0_arm64.whl CPython 3.12 CPython 3.12 macOS 11.0+ ARM64 Details for t1c_ir-0.0.2-cp312-cp312-macosx_11_0_arm64.whl
t1c_ir-0.0.2-cp311-cp311-win_amd64.whl CPython 3.11 CPython 3.11 Windows x86-64 Details for t1c_ir-0.0.2-cp311-cp311-win_amd64.whl
t1c_ir-0.0.2-cp311-cp311-win32.whl CPython 3.11 CPython 3.11 Windows x86-32 Details for t1c_ir-0.0.2-cp311-cp311-win32.whl
t1c_ir-0.0.2-cp311-cp311-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl CPython 3.11 CPython 3.11 Linux glibc 2.17+ x86-64, Linux glibc 2.28+ x86-64 Details for t1c_ir-0.0.2-cp311-cp311-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
t1c_ir-0.0.2-cp311-cp311-macosx_11_0_arm64.whl CPython 3.11 CPython 3.11 macOS 11.0+ ARM64 Details for t1c_ir-0.0.2-cp311-cp311-macosx_11_0_arm64.whl
t1c_ir-0.0.2-cp310-cp310-win_amd64.whl CPython 3.10 CPython 3.10 Windows x86-64 Details for t1c_ir-0.0.2-cp310-cp310-win_amd64.whl
t1c_ir-0.0.2-cp310-cp310-win32.whl CPython 3.10 CPython 3.10 Windows x86-32 Details for t1c_ir-0.0.2-cp310-cp310-win32.whl
t1c_ir-0.0.2-cp310-cp310-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl CPython 3.10 CPython 3.10 Linux glibc 2.17+ x86-64, Linux glibc 2.28+ x86-64 Details for t1c_ir-0.0.2-cp310-cp310-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
t1c_ir-0.0.2-cp310-cp310-macosx_11_0_arm64.whl CPython 3.10 CPython 3.10 macOS 11.0+ ARM64 Details for t1c_ir-0.0.2-cp310-cp310-macosx_11_0_arm64.whl

Total release size: 18.5 MB

Release files / t1c_ir-0.0.2-cp313-cp313-win_amd64.whl

Download URL t1c_ir-0.0.2-cp313-cp313-win_amd64.whl
Size 457.7 kB
Tags CPython 3.13 Windows x86-64
SHA-256 checksum
How to use checksums
17eb4f3c01f78875d258be85cb24fc29171eb0f806084ffe956ba9df5f10c42b
BLAKE2b-256 checksum
How to use checksums
92aa54d959c4ca3d29bbc0da311addeb5c58df017e1ab6c092fa984a016a3847
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.7

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 Feb 4, 2026.

Transparency log

Release files / t1c_ir-0.0.2-cp313-cp313-win32.whl

Download URL t1c_ir-0.0.2-cp313-cp313-win32.whl
Size 401.8 kB
Tags CPython 3.13 Windows x86-32
SHA-256 checksum
How to use checksums
cefdca14bd408b120780b95e3f30e4dfd38e9e7d00cd84eb4a9ee01daaa6f123
BLAKE2b-256 checksum
How to use checksums
697c59f5df7aaa4ee7926d3d189bac6df6c0ea0a20c3c50aa5665652751a6def
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.7

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 Feb 4, 2026.

Transparency log

Release files / t1c_ir-0.0.2-cp313-cp313-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl

Download URL t1c_ir-0.0.2-cp313-cp313-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
Size 3.3 MB
Tags CPython 3.13 Linux glibc 2.17+ x86-64 Linux glibc 2.28+ x86-64
SHA-256 checksum
How to use checksums
8be2676318b7179786f5a6368113af6d67c283609898388d6dc007beee21415d
BLAKE2b-256 checksum
How to use checksums
6e9ec56407dcecef53ce34511c50ef58b2fe24d7dcc084ffcccb1a622ba44105
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.7

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 Feb 4, 2026.

Transparency log

Release files / t1c_ir-0.0.2-cp313-cp313-macosx_11_0_arm64.whl

Download URL t1c_ir-0.0.2-cp313-cp313-macosx_11_0_arm64.whl
Size 490.2 kB
Tags CPython 3.13 macOS 11.0+ ARM64
SHA-256 checksum
How to use checksums
538fb24e8f77ecd3becc67f8d411782f5f37819b8ce89e629b5c4536060e4718
BLAKE2b-256 checksum
How to use checksums
64581168d01de15b16aa35077c27c3a14e7220aedbb506bf3f3921adb50e70c7
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.7

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 Feb 4, 2026.

Transparency log

Release files / t1c_ir-0.0.2-cp312-cp312-win_amd64.whl

Download URL t1c_ir-0.0.2-cp312-cp312-win_amd64.whl
Size 464.2 kB
Tags CPython 3.12 Windows x86-64
SHA-256 checksum
How to use checksums
e817c1b07c72d76b691784c6aa188796fa2e2b3a016479dbd08d40a9a41034d9
BLAKE2b-256 checksum
How to use checksums
a4c1b7177e87daa8ac2ab28ce2f915604777a8f035dca302c620c9dc1848e3fd
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.7

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 Feb 4, 2026.

Transparency log

Release files / t1c_ir-0.0.2-cp312-cp312-win32.whl

Download URL t1c_ir-0.0.2-cp312-cp312-win32.whl
Size 406.6 kB
Tags CPython 3.12 Windows x86-32
SHA-256 checksum
How to use checksums
9e27d695f5ee801bf6ed0db396f4da5c156b0d55b757625bf546ef8f5864c3e2
BLAKE2b-256 checksum
How to use checksums
67122c6d271731593bcbba05de2f1a6361415ccdc3c29b9ccf29d20f410efb56
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.7

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 Feb 4, 2026.

Transparency log

Release files / t1c_ir-0.0.2-cp312-cp312-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl

Download URL t1c_ir-0.0.2-cp312-cp312-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
Size 3.4 MB
Tags CPython 3.12 Linux glibc 2.17+ x86-64 Linux glibc 2.28+ x86-64
SHA-256 checksum
How to use checksums
7922cb570db325abff8911f1d02ababff2f63b4fc4744be3a1901db5cc06b8e2
BLAKE2b-256 checksum
How to use checksums
a8e48e33e351f97b0d3b4bbe274781f29ea788e71d42adb55c561fc896a9aa97
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.7

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 Feb 4, 2026.

Transparency log

Release files / t1c_ir-0.0.2-cp312-cp312-macosx_11_0_arm64.whl

Download URL t1c_ir-0.0.2-cp312-cp312-macosx_11_0_arm64.whl
Size 496.1 kB
Tags CPython 3.12 macOS 11.0+ ARM64
SHA-256 checksum
How to use checksums
e96161d85bab22b6efac26c011da8c78c861b15a5392053f521dba85ffd1b7de
BLAKE2b-256 checksum
How to use checksums
b4280c160334a4761d4f8cc3b7cfb1e151668c0372928000e2044714354477c4
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.7

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 Feb 4, 2026.

Transparency log

Release files / t1c_ir-0.0.2-cp311-cp311-win_amd64.whl

Download URL t1c_ir-0.0.2-cp311-cp311-win_amd64.whl
Size 470.9 kB
Tags CPython 3.11 Windows x86-64
SHA-256 checksum
How to use checksums
6816f531c7f71d5ce8d0be804ed79aeeedad59bc1bcbaed8d8633f4b56d7eebc
BLAKE2b-256 checksum
How to use checksums
f29058f0e6b02538f025b672132216f66f9a94b6eb260afb82c9c17412a9052c
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.7

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 Feb 4, 2026.

Transparency log

Release files / t1c_ir-0.0.2-cp311-cp311-win32.whl

Download URL t1c_ir-0.0.2-cp311-cp311-win32.whl
Size 419.8 kB
Tags CPython 3.11 Windows x86-32
SHA-256 checksum
How to use checksums
40dca7cafa8bbb65ebaafa501c6fece2190ff4896936ac41f7ac03e49b1e47b0
BLAKE2b-256 checksum
How to use checksums
6c2306fb49dfb86a1e14a8dca8e505c02e60589f2100783dfeb79cd89328b95c
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.7

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 Feb 4, 2026.

Transparency log

Release files / t1c_ir-0.0.2-cp311-cp311-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl

Download URL t1c_ir-0.0.2-cp311-cp311-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
Size 3.3 MB
Tags CPython 3.11 Linux glibc 2.17+ x86-64 Linux glibc 2.28+ x86-64
SHA-256 checksum
How to use checksums
15c0487fbe9aefe0d1eaa3ccfa733c8691bb4831cf486d10d9a20a7d42a74a91
BLAKE2b-256 checksum
How to use checksums
dbd629b80b3aec3aaab157a13cd30758d4e2e1b66b8570d7efbb96fe7ee59c58
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.7

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 Feb 4, 2026.

Transparency log

Release files / t1c_ir-0.0.2-cp311-cp311-macosx_11_0_arm64.whl

Download URL t1c_ir-0.0.2-cp311-cp311-macosx_11_0_arm64.whl
Size 496.5 kB
Tags CPython 3.11 macOS 11.0+ ARM64
SHA-256 checksum
How to use checksums
20729d4bfd63c8f1063a89b448aa28ce3ea4b8f01e46a1a862b711c1786f7189
BLAKE2b-256 checksum
How to use checksums
ceb8cf3090c6136d1982d502c7c1687787b622b4cf72d95d534c27dd32389920
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.7

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 Feb 4, 2026.

Transparency log

Release files / t1c_ir-0.0.2-cp310-cp310-win_amd64.whl

Download URL t1c_ir-0.0.2-cp310-cp310-win_amd64.whl
Size 472.0 kB
Tags CPython 3.10 Windows x86-64
SHA-256 checksum
How to use checksums
226f48f0b2018d029bf102686047996e465fd069e3cbab45f71fcecb66b5140e
BLAKE2b-256 checksum
How to use checksums
7332fd8cdb07cc1ef43a8976118c71a730f0150969b9fe25e9edfbd5aed49984
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.7

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 Feb 4, 2026.

Transparency log

Release files / t1c_ir-0.0.2-cp310-cp310-win32.whl

Download URL t1c_ir-0.0.2-cp310-cp310-win32.whl
Size 421.1 kB
Tags CPython 3.10 Windows x86-32
SHA-256 checksum
How to use checksums
a4b2a529a23c586b4732304e1dde112190506261efe5ddef5fa2fa469087a92e
BLAKE2b-256 checksum
How to use checksums
1bdfcb31c7c71b20e6225222028037fbeb67c1eda688e257b217af7d9e2e4c2e
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.7

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 Feb 4, 2026.

Transparency log

Release files / t1c_ir-0.0.2-cp310-cp310-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl

Download URL t1c_ir-0.0.2-cp310-cp310-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
Size 3.1 MB
Tags CPython 3.10 Linux glibc 2.17+ x86-64 Linux glibc 2.28+ x86-64
SHA-256 checksum
How to use checksums
95c6db07e3d2a0b9e3d808190e4686d902696d504aa7aefd67b67a6ccaca726f
BLAKE2b-256 checksum
How to use checksums
c7cbb22d06b9308c4054027d3e74e3620bd10397db94d9d282a3185a99ea6c92
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.7

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 Feb 4, 2026.

Transparency log

Release files / t1c_ir-0.0.2-cp310-cp310-macosx_11_0_arm64.whl

Download URL t1c_ir-0.0.2-cp310-cp310-macosx_11_0_arm64.whl
Size 500.5 kB
Tags CPython 3.10 macOS 11.0+ ARM64
SHA-256 checksum
How to use checksums
0d86f16b8589cfcc04177c83f00b429dcdba31db11e476328746b0130c6c820e
BLAKE2b-256 checksum
How to use checksums
354187a58a514f41bbf657ac80bd4c1ceff166363bff34d97473c52ada570ceb
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.7

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 Feb 4, 2026.

Transparency log

Security for t1c-ir 0.0.2

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 16 files in this release have been uploaded with provenance metadata.

Select from 16 files

Attestation for t1c_ir-0.0.2-cp313-cp313-win_amd64.whl

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 Feb 4, 2026.

Transparency log

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.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Release history Release notifications | RSS feed

This release

0.0.2 This release

16 release files Full provenance

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page