This release is a pre-release and may not be stable for production use.
copium
Makes Python deepcopy() fast.
Highlights
- ⚡ 4-28x faster on built-in types
- 🧠 ~30% less memory per copy
- ✨ requires zero code changes
- 🧪 passes Python's test_copy.py
- 📦 pre-built wheels for Python 3.10–3.14 on Linux/macOS/Windows (x64/ARM64)
- 🔓 passes all tests on free-threaded Python builds
Installation
pip install 'copium[autopatch]'
This will effortlessly make copy.deepcopy() fast in current environment.
For manual usage
pip install copium
Manual usage
import copium
assert copium.deepcopy(x := []) is not x
The copium module includes all public declarations of stdlib copy module, so it's generally safe
to:
- from copy import copy, deepcopy, Error
+ from copium import copy, deepcopy, Error
How is it so fast?
-
Zero interpreter overhead for built-in containers and atomic types
If your data consist only of the types below,
deepcopyoperation won't touch the interpreter:- natively supported containers:
tuple,dict,list,set,frozenset,bytearrayandtypes.MethodType - natively supported atomics:
type(None),int,str,bytes,float,bool,complex,types.EllipsisType,types.NotImplementedType,range,property,weakref.ref,re.Pattern,decimal.Decimal,fractions.Fraction,types.CodeType,types.FunctionType,types.BuiltinFunctionType,types.ModuleType
- natively supported containers:
-
Native memo
- no time spent on creating extra
intobject forid(x) - hash is computed once for lookup and reused to store the copy
- keepalive is a lightweight vector of pointers instead of a
list - memo object is not tracked in GC, unless stolen in custom
__deepcopy__
- no time spent on creating extra
-
Native reduce handling
When type's
__reduce__strictly follows the protocol,copiumhandles returned values natively, without interpreter overhead, the same way CPython pickle implementation does. -
Cached memo
Rather than creating a new memo object for each
deepcopyand discarding it after, copium stores one per thread and reuses it. Referenced objects are cleared, but some amount of memory stays reserved, avoiding malloc/free overhead for typical workloads. -
Zero overhead patch on Python 3.12+
deepcopyfunction object stays the same after patch, only itsvectorcallis changed.
Compatibility notes
copium.deepcopy() designed to be drop-in replacement for copy.deepcopy(),
still there are minor deviations from stdlib you should be aware of.
Pickle protocol
stdlib's copy tolerates some deviations from the pickle protocol that pickle itself reject
(see https://github.com/python/cpython/issues/141757).
copium strictly follows stdlib semantics: if __reduce__
returns a list instead of a tuple for args, or a mapping instead of a dict for kwargs,
copium will coerce them the same way stdlib would
(via *args unpacking, **kwargs merging, .items() iteration, etc.).
Errors from malformed __reduce__ results match what copy.deepcopy produces.
Memo handling
With native memo, custom __deepcopy__ receives a copium.memo,
which is fully compatible with how copy.deepcopy() uses it internally.
Per Python docs, custom __deepcopy__ methods should treat memo as an opaque object and just pass
it through in any subsequent deepcopy calls.
However, some native extensions that implement __deepcopy__ on their objects
may require exact dict object to be passed as memo argument.
Typically, in this case, they raise TypeError or AssertionError.
copium will attempt to recover by calling __deepcopy__ again with dict memo. If that second call
succeeds, a warning with clear suggestions will be emitted, otherwise the error will be raised as
is.
Example
>>> import copium
>>> class CustomType:
... def __deepcopy__(self, memo):
... if not isinstance(memo, dict):
... raise TypeError("I'm enforcing memo to be a dict")
... return self
...
>>> print("Copied successfully: ", copium.deepcopy(CustomType()))
<python-input-2>:1: UserWarning:
Seems like 'copium.memo' was rejected inside '__main__.CustomType.__deepcopy__':
Traceback (most recent call last):
File "<python-input-2>", line 1, in <module>
File "<python-input-1>", line 4, in __deepcopy__
raise TypeError("I'm enforcing memo to be a dict")
TypeError: I'm enforcing memo to be a dict
copium was able to recover from this error, but this is slow and unreliable.
Fix:
Per Python docs, '__main__.CustomType.__deepcopy__' should treat memo as an opaque object.
See: https://docs.python.org/3/library/copy.html#object.__deepcopy__
Workarounds:
local change deepcopy(CustomType()) to deepcopy(CustomType(), {})
-> copium uses dict memo in this call (recommended)
global export COPIUM_USE_DICT_MEMO=1
-> copium uses dict memo everywhere (~1.3-2x slowdown, still faster than stdlib)
silent export COPIUM_NO_MEMO_FALLBACK_WARNING='TypeError: I'm enforcing memo to be a dict'
-> 'deepcopy(CustomType())' stays slow to deepcopy
explosive export COPIUM_NO_MEMO_FALLBACK=1
-> 'deepcopy(CustomType())' raises the error above
Copied successfully: <__main__.CustomType object at 0x104d1cad0>
Credits
- @sobolevn for constructive feedback on C code / tests quality
- @eendebakpt for C implementation of parts of
copy.deepcopyin https://github.com/python/cpython/pull/91610 — used as early reference - @orsinium for svg.py — used to generate main chart
- @provencher for repoprompt.com — used it to build context for LLMs/editing
- Anthropic/OpenAI/xAI for translating my ideas to compilable C code and educating me on the subject
- One special lizard 🦎
1 maintainer
Metadata
1 maintainer
Release files for copium 0.1.0a1.dev167
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distributions (wheels)
Total release size: 11.6 MB
Release files / copium-0.1.0a1.dev167-cp314-cp314-win_arm64.whl
| Download URL | copium-0.1.0a1.dev167-cp314-cp314-win_arm64.whl |
|---|---|
| Size | 72.8 kB |
| Tags | CPython 3.14 Windows ARM64 |
|
SHA-256 checksum How to use checksums |
9f1728744afb8771f264b51ffecfdf1d7e5f95129f4fc502e4c6d216419e482f
|
|
BLAKE2b-256 checksum How to use checksums |
295c679b27f439034d6f0caacae3c1344024d4ce297a1995ed70467235d54e4b
|
| 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 Mar 7, 2026.
Transparency logRelease files / copium-0.1.0a1.dev167-cp314-cp314-win_amd64.whl
| Download URL | copium-0.1.0a1.dev167-cp314-cp314-win_amd64.whl |
|---|---|
| Size | 78.8 kB |
| Tags | CPython 3.14 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
24d921df2405892e7c62418a8c64522828d9b89c0a9e466929774ddce17e5077
|
|
BLAKE2b-256 checksum How to use checksums |
d851e0d40e82d7936b583de2e401f924d02ca365fae1418a5dcc56cf47d81f35
|
| 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 Mar 7, 2026.
Transparency logRelease files / copium-0.1.0a1.dev167-cp314-cp314-musllinux_1_2_x86_64.whl
| Download URL | copium-0.1.0a1.dev167-cp314-cp314-musllinux_1_2_x86_64.whl |
|---|---|
| Size | 521.8 kB |
| Tags | CPython 3.14 Linux musl 1.2+ x86-64 |
|
SHA-256 checksum How to use checksums |
22427c253d327937c044af6901d21d913d689ed220e006130f266006c9959d57
|
|
BLAKE2b-256 checksum How to use checksums |
d2c6de50a8e738f5d732b32af4c39b878aeae5a65f75ba411b6accc224c155be
|
| 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 Mar 7, 2026.
Transparency logRelease files / copium-0.1.0a1.dev167-cp314-cp314-musllinux_1_2_aarch64.whl
| Download URL | copium-0.1.0a1.dev167-cp314-cp314-musllinux_1_2_aarch64.whl |
|---|---|
| Size | 506.0 kB |
| Tags | CPython 3.14 Linux musl 1.2+ ARM64 |
|
SHA-256 checksum How to use checksums |
90d0b3663f338de88575e8234e5a62c470b571a86dba241d101efcb56a286b97
|
|
BLAKE2b-256 checksum How to use checksums |
d7906da836e34be962109b952a221dc3d83121d4d0be6f4b4e9c66bf9750971e
|
| 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 Mar 7, 2026.
Transparency logRelease files / copium-0.1.0a1.dev167-cp314-cp314-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
| Download URL | copium-0.1.0a1.dev167-cp314-cp314-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl |
|---|---|
| Size | 527.3 kB |
| Tags | CPython 3.14 Linux glibc 2.17+ x86-64 Linux glibc 2.28+ x86-64 |
|
SHA-256 checksum How to use checksums |
b52a27c78a7b1e23abce92dfbb69b328b8fc0ee6f57c92cce0893f71ed4830c2
|
|
BLAKE2b-256 checksum How to use checksums |
ab75b1e68ee6f35400989809c44786f40d49d883deee208b6b859458f68472cf
|
| 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 Mar 7, 2026.
Transparency logRelease files / copium-0.1.0a1.dev167-cp314-cp314-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl
| Download URL | copium-0.1.0a1.dev167-cp314-cp314-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl |
|---|---|
| Size | 522.1 kB |
| Tags | CPython 3.14 Linux glibc 2.17+ ARM64 Linux glibc 2.28+ ARM64 |
|
SHA-256 checksum How to use checksums |
8a4063974accb318e229062597fde398b8e57ad75fe244f5664eb9b9311e80bf
|
|
BLAKE2b-256 checksum How to use checksums |
adc6010f6c67dd1d027ed26aca4ccdd6ee895341a4309976a293d2f754e5dced
|
| 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 Mar 7, 2026.
Transparency logRelease files / copium-0.1.0a1.dev167-cp314-cp314-macosx_11_0_arm64.whl
| Download URL | copium-0.1.0a1.dev167-cp314-cp314-macosx_11_0_arm64.whl |
|---|---|
| Size | 92.5 kB |
| Tags | CPython 3.14 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
289e1575839637a4c3ce9deff97fc144b05bbd44f2a1a43a907bba8053c4b7be
|
|
BLAKE2b-256 checksum How to use checksums |
7df699bf3f3018aa0071617ae7a23d6bc3e42866d9e1a0c2ba8aca31cf7e5ef1
|
| 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 Mar 7, 2026.
Transparency logRelease files / copium-0.1.0a1.dev167-cp314-cp314-macosx_10_15_x86_64.whl
| Download URL | copium-0.1.0a1.dev167-cp314-cp314-macosx_10_15_x86_64.whl |
|---|---|
| Size | 91.6 kB |
| Tags | CPython 3.14 macOS 10.15+ x86-64 |
|
SHA-256 checksum How to use checksums |
d799928102cc809d18fa747bd02153ab0b00a23a9c5ce8ce921a085038246480
|
|
BLAKE2b-256 checksum How to use checksums |
0380a930d6950c1f825abf58821d5b492f075be20ffe5c6953224aadfd0cbb31
|
| 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 Mar 7, 2026.
Transparency logRelease files / copium-0.1.0a1.dev167-cp313-cp313-win_arm64.whl
| Download URL | copium-0.1.0a1.dev167-cp313-cp313-win_arm64.whl |
|---|---|
| Size | 67.7 kB |
| Tags | CPython 3.13 Windows ARM64 |
|
SHA-256 checksum How to use checksums |
136a3e9b5f946ac734f0fdda343285f17ad2e2f36323ebf4b6d37e00eb828f66
|
|
BLAKE2b-256 checksum How to use checksums |
1fc34f3a0e57f7efea8ea761ffca4c2e0493179add33fad56760b7f06762825f
|
| 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 Mar 7, 2026.
Transparency logRelease files / copium-0.1.0a1.dev167-cp313-cp313-win_amd64.whl
| Download URL | copium-0.1.0a1.dev167-cp313-cp313-win_amd64.whl |
|---|---|
| Size | 74.6 kB |
| Tags | CPython 3.13 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
a5f894395c17d03c6326cc93d34b0a4d26427cb6cb959d409aedfcd4d6592fc0
|
|
BLAKE2b-256 checksum How to use checksums |
37dbdff984ed02043e1a1dd9652afd8df0889d2fbfc844857ea3a212ffece983
|
| 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 Mar 7, 2026.
Transparency logRelease files / copium-0.1.0a1.dev167-cp313-cp313-musllinux_1_2_x86_64.whl
| Download URL | copium-0.1.0a1.dev167-cp313-cp313-musllinux_1_2_x86_64.whl |
|---|---|
| Size | 509.5 kB |
| Tags | CPython 3.13 Linux musl 1.2+ x86-64 |
|
SHA-256 checksum How to use checksums |
38a61d5dad3f199aca4ad1ca825dbd18cdf128656f102f5af335e6864aa33111
|
|
BLAKE2b-256 checksum How to use checksums |
81dc094f7deb59e0a25493d53c605635847aa9bcd39d56d6dd26f9bd631a92d2
|
| 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 Mar 7, 2026.
Transparency logRelease files / copium-0.1.0a1.dev167-cp313-cp313-musllinux_1_2_aarch64.whl
| Download URL | copium-0.1.0a1.dev167-cp313-cp313-musllinux_1_2_aarch64.whl |
|---|---|
| Size | 498.0 kB |
| Tags | CPython 3.13 Linux musl 1.2+ ARM64 |
|
SHA-256 checksum How to use checksums |
ee4d8dd880cc2460d4cc05aaa70aa3f0626ee6abd4a8733502d799458c6cab19
|
|
BLAKE2b-256 checksum How to use checksums |
a6939fe7e8caac5c0ecad6b2aec60c47c1fae10fdd48bfeeb3393ece8db660ed
|
| 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 Mar 7, 2026.
Transparency logRelease files / copium-0.1.0a1.dev167-cp313-cp313-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
| Download URL | copium-0.1.0a1.dev167-cp313-cp313-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl |
|---|---|
| Size | 513.6 kB |
| Tags | CPython 3.13 Linux glibc 2.17+ x86-64 Linux glibc 2.28+ x86-64 |
|
SHA-256 checksum How to use checksums |
e11f5901bd20f53fb53adc62d0ec17f9f402f49023fc58f4a65cc75ba6762647
|
|
BLAKE2b-256 checksum How to use checksums |
a7f4db89673800a088eb53da11f54507862c832bdd7a39642f665643d03c2bbb
|
| 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 Mar 7, 2026.
Transparency logRelease files / copium-0.1.0a1.dev167-cp313-cp313-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl
| Download URL | copium-0.1.0a1.dev167-cp313-cp313-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl |
|---|---|
| Size | 504.2 kB |
| Tags | CPython 3.13 Linux glibc 2.17+ ARM64 Linux glibc 2.28+ ARM64 |
|
SHA-256 checksum How to use checksums |
88d361c50fa7a9b389c9bdadc7e371077b82459600296f168af89d8e91ae8856
|
|
BLAKE2b-256 checksum How to use checksums |
49696fa369a25ff586b4416628cff3e01566c90320520526beaf497f7c0d42fc
|
| 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 Mar 7, 2026.
Transparency logRelease files / copium-0.1.0a1.dev167-cp313-cp313-macosx_11_0_arm64.whl
| Download URL | copium-0.1.0a1.dev167-cp313-cp313-macosx_11_0_arm64.whl |
|---|---|
| Size | 89.4 kB |
| Tags | CPython 3.13 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
808a0e9c575a807eb41c1d61c9c23b6c89e06ea95e20611ebd558c651c15ee45
|
|
BLAKE2b-256 checksum How to use checksums |
d3f361d530909a93c420d75d3d2d96f284260dc75a4ba556ad8738fa700f8572
|
| 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 Mar 7, 2026.
Transparency logRelease files / copium-0.1.0a1.dev167-cp313-cp313-macosx_10_13_x86_64.whl
| Download URL | copium-0.1.0a1.dev167-cp313-cp313-macosx_10_13_x86_64.whl |
|---|---|
| Size | 89.7 kB |
| Tags | CPython 3.13 macOS 10.13+ x86-64 |
|
SHA-256 checksum How to use checksums |
a2063c3cc7b72d68eedfb86a308b6a3fc97ba30f9ee128f7f5bf902ed1ddc44f
|
|
BLAKE2b-256 checksum How to use checksums |
3ee4b805493d111dd219d68bb5afe2460220ad02cb20095fbaea3d3ac7999b2f
|
| 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 Mar 7, 2026.
Transparency logRelease files / copium-0.1.0a1.dev167-cp312-cp312-win_arm64.whl
| Download URL | copium-0.1.0a1.dev167-cp312-cp312-win_arm64.whl |
|---|---|
| Size | 67.3 kB |
| Tags | CPython 3.12 Windows ARM64 |
|
SHA-256 checksum How to use checksums |
1f2cbf6de378a8d9a9d36acce25d98e36a31b94c06850ffc00d0e734b01f4651
|
|
BLAKE2b-256 checksum How to use checksums |
617feb2e105d53fe92c8a189724d1d594e6895291d472993622078efc4dc1636
|
| 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 Mar 7, 2026.
Transparency logRelease files / copium-0.1.0a1.dev167-cp312-cp312-win_amd64.whl
| Download URL | copium-0.1.0a1.dev167-cp312-cp312-win_amd64.whl |
|---|---|
| Size | 73.9 kB |
| Tags | CPython 3.12 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
ec2fcc10c3e7c0ca422aa7c995a6f864fff94faf94afbf0bb4056694ff925267
|
|
BLAKE2b-256 checksum How to use checksums |
49263fd88584c013d37b46caaff6a2036d5a2d46cd9e0ff89e3732911e2bf06e
|
| 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 Mar 7, 2026.
Transparency logRelease files / copium-0.1.0a1.dev167-cp312-cp312-musllinux_1_2_x86_64.whl
| Download URL | copium-0.1.0a1.dev167-cp312-cp312-musllinux_1_2_x86_64.whl |
|---|---|
| Size | 502.8 kB |
| Tags | CPython 3.12 Linux musl 1.2+ x86-64 |
|
SHA-256 checksum How to use checksums |
53efe9798efa60f1fc9b6cdbb7ed35f3a921846a4ddfd8ee467e5b3723251b15
|
|
BLAKE2b-256 checksum How to use checksums |
5ec3dce57c36039a2d32e6d297c6d8cf5f8ded7014f9805edd10aeeb36da421d
|
| 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 Mar 7, 2026.
Transparency logRelease files / copium-0.1.0a1.dev167-cp312-cp312-musllinux_1_2_aarch64.whl
| Download URL | copium-0.1.0a1.dev167-cp312-cp312-musllinux_1_2_aarch64.whl |
|---|---|
| Size | 491.7 kB |
| Tags | CPython 3.12 Linux musl 1.2+ ARM64 |
|
SHA-256 checksum How to use checksums |
da93208b77fcafd14e063dcd38ac2d1ca96314995a4c5a058069977f7bebab46
|
|
BLAKE2b-256 checksum How to use checksums |
2de30ab660161c2e979223cfdd6d932ebdcc10f0b1a432d1075c38dd8751b921
|
| 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 Mar 7, 2026.
Transparency logRelease files / copium-0.1.0a1.dev167-cp312-cp312-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
| Download URL | copium-0.1.0a1.dev167-cp312-cp312-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl |
|---|---|
| Size | 504.9 kB |
| Tags | CPython 3.12 Linux glibc 2.17+ x86-64 Linux glibc 2.28+ x86-64 |
|
SHA-256 checksum How to use checksums |
371a620ebe7c823ff1776886e234ce9e6be9b314bd0fa0d3a1b593fb6f99f2c9
|
|
BLAKE2b-256 checksum How to use checksums |
06a60ece5c5d32f7e47e222d5a4ec3d5c38be9954a75ccec0917017cf5302ed6
|
| 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 Mar 7, 2026.
Transparency logRelease files / copium-0.1.0a1.dev167-cp312-cp312-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl
| Download URL | copium-0.1.0a1.dev167-cp312-cp312-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl |
|---|---|
| Size | 497.9 kB |
| Tags | CPython 3.12 Linux glibc 2.17+ ARM64 Linux glibc 2.28+ ARM64 |
|
SHA-256 checksum How to use checksums |
e7218bbc7f9534f5146465c59f08936ed5a38b4ea9c3b5913e79dabd856273f8
|
|
BLAKE2b-256 checksum How to use checksums |
cf8a775aa7ed7351c43b5ad6c723f458936e640f334bb023bf276932e7046f25
|
| 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 Mar 7, 2026.
Transparency logRelease files / copium-0.1.0a1.dev167-cp312-cp312-macosx_11_0_arm64.whl
| Download URL | copium-0.1.0a1.dev167-cp312-cp312-macosx_11_0_arm64.whl |
|---|---|
| Size | 89.1 kB |
| Tags | CPython 3.12 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
a7794184ed105ceec3ef9cac5116fbbceb49783b1562cdbd942376e793be6cef
|
|
BLAKE2b-256 checksum How to use checksums |
b32d4f63d3b98fd5939d3bb8007d3cb1af6d3db25768fe0cfc1e5b24c810dfd9
|
| 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 Mar 7, 2026.
Transparency logRelease files / copium-0.1.0a1.dev167-cp312-cp312-macosx_10_13_x86_64.whl
| Download URL | copium-0.1.0a1.dev167-cp312-cp312-macosx_10_13_x86_64.whl |
|---|---|
| Size | 89.2 kB |
| Tags | CPython 3.12 macOS 10.13+ x86-64 |
|
SHA-256 checksum How to use checksums |
240a940215d61d25ab8c9ea952fc1486b6b04fe576d8decefb7756aa068db29f
|
|
BLAKE2b-256 checksum How to use checksums |
33185d73422de124101cc343ec4463f8c81b526bcde2b173272061dc0e10ef13
|
| 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 Mar 7, 2026.
Transparency logRelease files / copium-0.1.0a1.dev167-cp311-cp311-win_arm64.whl
| Download URL | copium-0.1.0a1.dev167-cp311-cp311-win_arm64.whl |
|---|---|
| Size | 67.2 kB |
| Tags | CPython 3.11 Windows ARM64 |
|
SHA-256 checksum How to use checksums |
54f32b2a421134875bdc3f1c2c572257b3a1f04655658823045ab1f57ede2392
|
|
BLAKE2b-256 checksum How to use checksums |
2710943582ac897673ca2c8e7153e7af7f27681be2e25462a51bb913a4c68d75
|
| 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 Mar 7, 2026.
Transparency logRelease files / copium-0.1.0a1.dev167-cp311-cp311-win_amd64.whl
| Download URL | copium-0.1.0a1.dev167-cp311-cp311-win_amd64.whl |
|---|---|
| Size | 73.5 kB |
| Tags | CPython 3.11 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
6cd271233ebf41811c87891cff8104f47bcf4cc492de8f46a8791408a4b50ea4
|
|
BLAKE2b-256 checksum How to use checksums |
5b182f4888b3c1257d4be79ef956d30840bc8289a6676a5cc0b26b5eb945d9bf
|
| 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 Mar 7, 2026.
Transparency logRelease files / copium-0.1.0a1.dev167-cp311-cp311-musllinux_1_2_x86_64.whl
| Download URL | copium-0.1.0a1.dev167-cp311-cp311-musllinux_1_2_x86_64.whl |
|---|---|
| Size | 490.9 kB |
| Tags | CPython 3.11 Linux musl 1.2+ x86-64 |
|
SHA-256 checksum How to use checksums |
1bdf6a1abe40ed13b48e5de83489f0dfa3d69a98d2be8f0230e7cc7ce315a3d0
|
|
BLAKE2b-256 checksum How to use checksums |
f3a0fb624be6407fc74cd1246941b7863ed73f024b1cc3011e2ddc4aa56c510e
|
| 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 Mar 7, 2026.
Transparency logRelease files / copium-0.1.0a1.dev167-cp311-cp311-musllinux_1_2_aarch64.whl
| Download URL | copium-0.1.0a1.dev167-cp311-cp311-musllinux_1_2_aarch64.whl |
|---|---|
| Size | 481.7 kB |
| Tags | CPython 3.11 Linux musl 1.2+ ARM64 |
|
SHA-256 checksum How to use checksums |
6eee9cf393967d7722baf2ea331d6050d847654b599ebb355dba5aa8818eae8b
|
|
BLAKE2b-256 checksum How to use checksums |
3cd2d5d8b206cfeca6e886a15be71aea9efbb49b3722d8a4dfa836d2aed5c66a
|
| 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 Mar 7, 2026.
Transparency logRelease files / copium-0.1.0a1.dev167-cp311-cp311-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
| Download URL | copium-0.1.0a1.dev167-cp311-cp311-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl |
|---|---|
| Size | 492.3 kB |
| Tags | CPython 3.11 Linux glibc 2.17+ x86-64 Linux glibc 2.28+ x86-64 |
|
SHA-256 checksum How to use checksums |
768cdfcdf73fe0d311091e49212f6f17383c4574ced12a612db95c8f8cca012d
|
|
BLAKE2b-256 checksum How to use checksums |
1aaac7d8dbc6ea65e2d01bc8fc594f21e43d6d898c19fa41a8dfeb275b5d5d7e
|
| 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 Mar 7, 2026.
Transparency logRelease files / copium-0.1.0a1.dev167-cp311-cp311-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl
| Download URL | copium-0.1.0a1.dev167-cp311-cp311-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl |
|---|---|
| Size | 489.3 kB |
| Tags | CPython 3.11 Linux glibc 2.17+ ARM64 Linux glibc 2.28+ ARM64 |
|
SHA-256 checksum How to use checksums |
4cd48c53b8551104cf1e2136b45f8483835e80febb6e3d41642f2ed498d73bb3
|
|
BLAKE2b-256 checksum How to use checksums |
62ea3507c1c7bea7f2e6925e07677e98e8cfaa46fe009dfde33c6bd1372b64ae
|
| 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 Mar 7, 2026.
Transparency logRelease files / copium-0.1.0a1.dev167-cp311-cp311-macosx_11_0_arm64.whl
| Download URL | copium-0.1.0a1.dev167-cp311-cp311-macosx_11_0_arm64.whl |
|---|---|
| Size | 88.2 kB |
| Tags | CPython 3.11 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
fe6a332170533f9a54d5892fc7cbc2739cc7e85dc165fe99987d981083751cf1
|
|
BLAKE2b-256 checksum How to use checksums |
8eda056a4e92186854d936ad21aa83f770bdddae55bd978883fa8c175e291e95
|
| 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 Mar 7, 2026.
Transparency logRelease files / copium-0.1.0a1.dev167-cp311-cp311-macosx_10_9_x86_64.whl
| Download URL | copium-0.1.0a1.dev167-cp311-cp311-macosx_10_9_x86_64.whl |
|---|---|
| Size | 88.1 kB |
| Tags | CPython 3.11 macOS 10.9+ x86-64 |
|
SHA-256 checksum How to use checksums |
6c73de2bcc1e0b2fc6c5e1ff98565815fc8de33329fb5ed08e1dbe160e4b963c
|
|
BLAKE2b-256 checksum How to use checksums |
75f617fb961754292646595aa1071801711426e93699a0938df5d512b6735a9f
|
| 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 Mar 7, 2026.
Transparency logRelease files / copium-0.1.0a1.dev167-cp310-cp310-win_arm64.whl
| Download URL | copium-0.1.0a1.dev167-cp310-cp310-win_arm64.whl |
|---|---|
| Size | 67.7 kB |
| Tags | CPython 3.10 Windows ARM64 |
|
SHA-256 checksum How to use checksums |
8bdfa99cc68bb4d542c6d3cf979f192bb9afd519b854806c930b3beacfdfcb7a
|
|
BLAKE2b-256 checksum How to use checksums |
a85a48c4f52bc093fb3c8b9746673a002da8023b40914332baac1ff3e338a2eb
|
| 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 Mar 7, 2026.
Transparency logRelease files / copium-0.1.0a1.dev167-cp310-cp310-win_amd64.whl
| Download URL | copium-0.1.0a1.dev167-cp310-cp310-win_amd64.whl |
|---|---|
| Size | 74.0 kB |
| Tags | CPython 3.10 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
fb48a43b9ec6211710a446ad182df4d0792b4d69bf747d9ca829c024f60afcc3
|
|
BLAKE2b-256 checksum How to use checksums |
a30db127610e750cfe8c51ed07db42c7e35f77c99bda38a9c5e6580e1a0fb059
|
| 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 Mar 7, 2026.
Transparency logRelease files / copium-0.1.0a1.dev167-cp310-cp310-musllinux_1_2_x86_64.whl
| Download URL | copium-0.1.0a1.dev167-cp310-cp310-musllinux_1_2_x86_64.whl |
|---|---|
| Size | 492.7 kB |
| Tags | CPython 3.10 Linux musl 1.2+ x86-64 |
|
SHA-256 checksum How to use checksums |
bd2487e52d1b844e540c99930809d14aae7ca47d526292cc31be7df03011c0bf
|
|
BLAKE2b-256 checksum How to use checksums |
e7beabc6b9e8874aab308d05dcae652c449fb9ac181e7d71ed9c86d6d06e5448
|
| 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 Mar 7, 2026.
Transparency logRelease files / copium-0.1.0a1.dev167-cp310-cp310-musllinux_1_2_aarch64.whl
| Download URL | copium-0.1.0a1.dev167-cp310-cp310-musllinux_1_2_aarch64.whl |
|---|---|
| Size | 483.4 kB |
| Tags | CPython 3.10 Linux musl 1.2+ ARM64 |
|
SHA-256 checksum How to use checksums |
ae6dc899efd5e32736f53e7581ab4b01ea906a6f68e1388bef9facc305972773
|
|
BLAKE2b-256 checksum How to use checksums |
455e6763cf6d90734c89b43ec88a1d898c1add60f79c8c1725736bb5d29eb936
|
| 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 Mar 7, 2026.
Transparency logRelease files / copium-0.1.0a1.dev167-cp310-cp310-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
| Download URL | copium-0.1.0a1.dev167-cp310-cp310-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl |
|---|---|
| Size | 493.8 kB |
| Tags | CPython 3.10 Linux glibc 2.17+ x86-64 Linux glibc 2.28+ x86-64 |
|
SHA-256 checksum How to use checksums |
221f85beab4eb88582ae5257f1cc01ef76b3f8159dca45d69e1f406d6f5faeae
|
|
BLAKE2b-256 checksum How to use checksums |
072b7365c6389ac51f5847b14142b3d3b602e05ad4dd3c812cb9896d780a63cc
|
| 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 Mar 7, 2026.
Transparency logRelease files / copium-0.1.0a1.dev167-cp310-cp310-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl
| Download URL | copium-0.1.0a1.dev167-cp310-cp310-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl |
|---|---|
| Size | 488.2 kB |
| Tags | CPython 3.10 Linux glibc 2.17+ ARM64 Linux glibc 2.28+ ARM64 |
|
SHA-256 checksum How to use checksums |
96d541d095d04e13d4c979fd216f575e096af418059e201ceef30ae899560623
|
|
BLAKE2b-256 checksum How to use checksums |
e7271acacde2b9699df0f051a295723b20f7e5c30ea09601129df56677efafd1
|
| 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 Mar 7, 2026.
Transparency logRelease files / copium-0.1.0a1.dev167-cp310-cp310-macosx_11_0_arm64.whl
| Download URL | copium-0.1.0a1.dev167-cp310-cp310-macosx_11_0_arm64.whl |
|---|---|
| Size | 90.0 kB |
| Tags | CPython 3.10 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
99daa723a24e13437bb781fd920fc062b11152bf585d3ec6ba93f11ad25071b4
|
|
BLAKE2b-256 checksum How to use checksums |
11e7b5700e3e170b0bc7f5f2c274096744e2e9b52f2ac8681f21d9a3d682c2d7
|
| 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 Mar 7, 2026.
Transparency logRelease files / copium-0.1.0a1.dev167-cp310-cp310-macosx_10_9_x86_64.whl
| Download URL | copium-0.1.0a1.dev167-cp310-cp310-macosx_10_9_x86_64.whl |
|---|---|
| Size | 89.1 kB |
| Tags | CPython 3.10 macOS 10.9+ x86-64 |
|
SHA-256 checksum How to use checksums |
fc936cc7bc1d7890f329802978e7067d6810e870c1d2783ac709c6a3bab02b05
|
|
BLAKE2b-256 checksum How to use checksums |
50d73e06bcfe59bf277a2bba46bff26dba5de872ca26542ab78179f76664ba09
|
| 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 Mar 7, 2026.
Transparency logSecurity for copium 0.1.0a1.dev167
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 40 files in this release have been uploaded with provenance metadata.
Attestation for copium-0.1.0a1.dev167-cp314-cp314-win_arm64.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 Mar 7, 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.
