depccg
Codebase for A* CCG Parsing with a Supertag and Dependency Factored Model
Changes in v3
- The English and Japanese pretrained models run on PyTorch.
- Chainer and AllenNLP are no longer runtime dependencies.
- The package supports Python 3.10 and newer.
Requirements
- Python >= 3.10
- A C++ compiler supporting C++11 standard (in case of gcc, must be >= 4.8)
Installation
Using pip:
➜ pip install depccg
Development
Project metadata and dependencies are defined in pyproject.toml and locked in
uv.lock. To create a reproducible development environment and run the tests:
➜ uv sync --frozen
➜ uv run --frozen pytest
To build the source distribution and wheel:
➜ uv build
setup.py is retained only for the native Cython/C++ extension definitions;
package metadata and dependencies must be changed in pyproject.toml.
Usage
Using a pretrained English parser
The following English models run on PyTorch without Chainer or AllenNLP:
| Name | Description | unlabeled/labeled F1 on CCGbank | Download |
|---|---|---|---|
| basic | model trained on the combination of CCGbank and tri-training dataset (Yoshikawa et al., 2017) | 94.0%/88.8% | link (189M) |
elmo |
basic model with its embeddings replaced with ELMo (Peters et al., 2018) | 94.98%/90.51% | link (649M) |
rebank |
basic model trained on Rebanked CCGbank (Honnibal et al., 2010) | - | link (337M) |
The basic model is available by:
➜ depccg_en download
Downloaded models are stored under ~/.cache/depccg by default. Set
DEPCCG_HOME to use a different directory.
To use:
➜ echo "this is a test sentence ." | depccg_en
ID=1, Prob=-0.0006299018859863281
(<T S[dcl] 0 2> (<T S[dcl] 0 2> (<L NP XX XX this NP>) (<T S[dcl]\NP 0 2> (<L (S[dcl]\NP)/NP XX XX is (S[dcl]\NP)/NP>) (<T NP 0 2> (<L NP[nb]/N XX XX a NP[nb]/N>) (<T N 0 2> (<L N/N XX XX test N/N>) (<L N XX XX sentence N>) ) ) ) ) (<L . XX XX . .>) )
The ELMo and Rebank models can be downloaded and selected by name:
➜ depccg_en download elmo
➜ echo "this is a test sentence ." | depccg_en --model elmo
➜ depccg_en download rebank
➜ echo "this is a test sentence ." | depccg_en --model rebank
The old elmo_rebank file is no longer available and is not included in v3.
You can also pass a PyTorch model directory with --model.
Using a GPU (by --gpu option) is recommended if possible.
There are several output formats (see below).
➜ echo "this is a test sentence ." | depccg_en --format deriv
ID=1, Prob=-0.0006299018859863281
this is a test sentence .
NP (S[dcl]\NP)/NP NP[nb]/N N/N N .
---------------->
N
-------------------------->
NP
------------------------------------------>
S[dcl]\NP
------------------------------------------------<
S[dcl]
---------------------------------------------------<rp>
S[dcl]
By default, the input is expected to be pre-tokenized. If you want to process untokenized sentences, you can pass --tokenize option.
The POS and NER tags in the output are filled with XX by default. You can replace them with ones predicted using SpaCy:
➜ echo "this is a test sentence ." | depccg_en --annotator spacy
ID=1, Prob=-0.0006299018859863281
(<T S[dcl] 0 2> (<T S[dcl] 0 2> (<L NP DT DT this NP>) (<T S[dcl]\NP 0 2> (<L (S[dcl]\NP)/NP VBZ VBZ is (S[dcl]\NP)/NP>) (<T NP 0 2> (<L NP[nb]/N DT DT a NP[nb]/N>) (<T N 0 2> (<L N/N NN NN test N/N>) (<L N NN NN sentence N>) ) ) ) ) (<L . . . . .>) )
The parser uses a SpaCy's en_core_web_sm model.
Orelse, you can use POS/NER taggers implemented in C&C, which may be useful in some sorts of parsing experiments:
➜ export CANDC=/path/to/candc
➜ echo "this is a test sentence ." | depccg_en --annotator candc
ID=1, log prob=-0.0006299018859863281
(<T S[dcl] 0 2> (<T S[dcl] 0 2> (<L NP DT DT this NP>) (<T S[dcl]\NP 0 2> (<L (S[dcl]\NP)/NP VBZ VBZ is (S[dcl]\NP)/NP>) (<T NP 0 2> (<L NP[nb]/N DT DT a NP[nb]/N>) (<T N 0 2> (<L N/N NN NN test N/N>) (<L N NN NN sentence N>) ) ) ) ) (<L . . . . .>) )
By default, depccg expects the POS and NER models are placed in $CANDC/models/pos and $CANDC/models/ner, but you can explicitly specify them by setting CANDC_MODEL_POS and CANDC_MODEL_NER environmental variables.
It is also possible to obtain logical formulas using ccg2lambda's semantic parsing algorithm.
➜ echo "This is a test sentence ." | depccg_en --format ccg2lambda --annotator spacy
ID=0 log probability=-0.0006299018859863281
exists x.(_this(x) & exists z1.(_sentence(z1) & _test(z1) & (x = z1)))
Using a pretrained Japanese parser
The best performing model is available by:
➜ depccg_ja download
It can be downloaded directly here (56M).
The parser provides the almost same interface as with the English one, with slight differences including the default output format, which is now one compatible with the Japanese CCGbank:
➜ echo "これはテストの文です。" | depccg_ja
ID=1, Prob=-53.98793411254883
{< S[mod=nm,form=base,fin=t] {< S[mod=nm,form=base,fin=f] {< NP[case=nc,mod=nm,fin=f] {NP[case=nc,mod=nm,fin=f] これ/これ/**} {NP[case=nc,mod=nm,fin=f]\NP[case=nc,mod=nm,fin=f] は/は/**}} {< S[mod=nm,form=base,fin=f]\NP[case=nc,mod=nm,fin=f] {< NP[case=nc,mod=nm,fin=f] {< NP[case=nc,mod=nm,fin=f] {NP[case=nc,mod=nm,fin=f] テスト/テスト/**} {NP[case=nc,mod=nm,fin=f]\NP[case=nc,mod=nm,fin=f] の/の/**}} {NP[case=nc,mod=nm,fin=f]\NP[case=nc,mod=nm,fin=f] 文/文/**}} {(S[mod=nm,form=base,fin=f]\NP[case=nc,mod=nm,fin=f])\NP[case=nc,mod=nm,fin=f] です/です/**}}} {S[mod=nm,form=base,fin=t]\S[mod=nm,form=base,fin=f] 。/。/**}}
You can pass pre-tokenized sentences as well:
➜ echo "これ は テスト の 文 です 。" | depccg_ja --pre-tokenized
ID=1, Prob=-53.98793411254883
{< S[mod=nm,form=base,fin=t] {< S[mod=nm,form=base,fin=f] {< NP[case=nc,mod=nm,fin=f] {NP[case=nc,mod=nm,fin=f] これ/これ/**} {NP[case=nc,mod=nm,fin=f]\NP[case=nc,mod=nm,fin=f] は/は/**}} {< S[mod=nm,form=base,fin=f]\NP[case=nc,mod=nm,fin=f] {< NP[case=nc,mod=nm,fin=f] {< NP[case=nc,mod=nm,fin=f] {NP[case=nc,mod=nm,fin=f] テスト/テスト/**} {NP[case=nc,mod=nm,fin=f]\NP[case=nc,mod=nm,fin=f] の/の/**}} {NP[case=nc,mod=nm,fin=f]\NP[case=nc,mod=nm,fin=f] 文/文/**}} {(S[mod=nm,form=base,fin=f]\NP[case=nc,mod=nm,fin=f])\NP[case=nc,mod=nm,fin=f] です/です/**}}} {S[mod=nm,form=base,fin=t]\S[mod=nm,form=base,fin=f] 。/。/**}}
Available output formats
auto- the most standard format following AUTO format in the English CCGbankauto_extended- extension of auto format with combinator info and POS/NER tagsderiv- visualized derivations in ASCII artxml- XML format compatible with C&C's XML format (only for English parsing)conll- CoNLL formathtml- visualized trees in MathMLprolog- Prolog-like formatjigg_xml- XML format compatible with Jiggptb- Penn Treebank-style formatccg2lambda- logical formula converted from a derivation using ccg2lambdajigg_xml_ccg2lambda- jigg_xml format with ccg2lambda logical formula insertedjson- JSON formatja- a format adopted in Japanese CCGbank (only for Japanese)
Programmatic Usage
Please look into depccg/__main__.py.
Evaluation in terms of predicate-argument dependencies
The standard CCG parsing evaluation can be performed with the following script:
➜ cat ccgbank/data/PARG/00/* > wsj_00.parg
➜ export CANDC=/path/to/candc
➜ python -m depccg.tools.evaluate wsj_00.parg wsj_00.predicted.auto
The script is dependent on C&C's generate program, which is only available by compiling the C&C program from the source.
(Currently, the above page is down. You can find the C&C parser here or here)
Miscellaneous
Diff tool
In error analysis, you must want to see diffs between trees in an intuitive way.
depccg.tools.diff does exactly this:
➜ python -m depccg.tools.diff file1.auto file2.auto > diff.html
which outputs:
where trees in the same lines of the files are compared and the diffs are marked in color.
Citation
If you make use of this software, please cite the following:
@inproceedings{yoshikawa:2017acl,
author={Yoshikawa, Masashi and Noji, Hiroshi and Matsumoto, Yuji},
title={A* CCG Parsing with a Supertag and Dependency Factored Model},
booktitle={Proceedings of the 55th Annual Meeting of the Association for Computational Linguistics (Volume 1: Long Papers)},
publisher={Association for Computational Linguistics},
year={2017},
pages={277--287},
location={Vancouver, Canada},
doi={10.18653/v1/P17-1026},
url={http://aclweb.org/anthology/P17-1026}
}
Licence
MIT Licence
Contact
For questions and usage issues, please contact yoshikawa@tohoku.jp.
Acknowledgement
In creating the parser, I owe very much to:
Metadata
Release files for depccg 3.0.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| depccg-3.0.0.tar.gz | 1.0 MB | With provenance | Details |
Built distributions (wheels)
Total release size: 25.6 MB
Release files / depccg-3.0.0.tar.gz
| Download URL | depccg-3.0.0.tar.gz |
|---|---|
| Size | 1.0 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e18f85ccd14af9c29eb803c259cb7a05229864b998690e15bd51580096732ddc
|
|
BLAKE2b-256 checksum How to use checksums |
85ff752f5146ef124738f5c392a479ea8987a6aac74ae8c514ff96345dde6a1f
|
| 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 15, 2026.
Transparency logRelease files / depccg-3.0.0-cp314-cp314-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
| Download URL | depccg-3.0.0-cp314-cp314-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl |
|---|---|
| Size | 1.7 MB |
| Tags | CPython 3.14 Linux glibc 2.27+ x86-64 Linux glibc 2.28+ x86-64 |
|
SHA-256 checksum How to use checksums |
24cae88b6be08a6e1140a6492bd2793c1ed5ebd899547c1f2dd33283f4911561
|
|
BLAKE2b-256 checksum How to use checksums |
d9f2eb4bde7584e1eb80998679ba0d3c94656c537eb7f39aaca371adc1a66cef
|
| 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 15, 2026.
Transparency logRelease files / depccg-3.0.0-cp314-cp314-manylinux_2_27_aarch64.manylinux_2_28_aarch64.whl
| Download URL | depccg-3.0.0-cp314-cp314-manylinux_2_27_aarch64.manylinux_2_28_aarch64.whl |
|---|---|
| Size | 1.7 MB |
| Tags | CPython 3.14 Linux glibc 2.27+ ARM64 Linux glibc 2.28+ ARM64 |
|
SHA-256 checksum How to use checksums |
5eb85c50c61d216e27f109ec5692ecc07650c5e1fe7d405978e1a3c08bc96147
|
|
BLAKE2b-256 checksum How to use checksums |
6562e783a96c39d69da0112ca8a529c9550b2c780e3028701abaf2f3995c7551
|
| 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 15, 2026.
Transparency logRelease files / depccg-3.0.0-cp314-cp314-macosx_11_0_arm64.whl
| Download URL | depccg-3.0.0-cp314-cp314-macosx_11_0_arm64.whl |
|---|---|
| Size | 951.3 kB |
| Tags | CPython 3.14 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
a21fd93f8cfc2387b2b1fd726892d134aed5e608e82e630017cccbbfb517e241
|
|
BLAKE2b-256 checksum How to use checksums |
129827ef6397105c892525aaae72a86d197aad589368402b4a51f4d3f8704c32
|
| 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 15, 2026.
Transparency logRelease files / depccg-3.0.0-cp313-cp313-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
| Download URL | depccg-3.0.0-cp313-cp313-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl |
|---|---|
| Size | 1.7 MB |
| Tags | CPython 3.13 Linux glibc 2.27+ x86-64 Linux glibc 2.28+ x86-64 |
|
SHA-256 checksum How to use checksums |
b3e716a57d8a83103fd938266b04461478d2e5e5c17211fce41f18b7a3ef5870
|
|
BLAKE2b-256 checksum How to use checksums |
4290d446d1b6976884d7e905f808e0551616584ead6e6e2c2dbeee675d7e0821
|
| 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 15, 2026.
Transparency logRelease files / depccg-3.0.0-cp313-cp313-manylinux_2_27_aarch64.manylinux_2_28_aarch64.whl
| Download URL | depccg-3.0.0-cp313-cp313-manylinux_2_27_aarch64.manylinux_2_28_aarch64.whl |
|---|---|
| Size | 1.7 MB |
| Tags | CPython 3.13 Linux glibc 2.27+ ARM64 Linux glibc 2.28+ ARM64 |
|
SHA-256 checksum How to use checksums |
a9dcd3be0416f1aba181b5393e23f02525abdff88ef8f2bf8d0e1801c8f7b0d1
|
|
BLAKE2b-256 checksum How to use checksums |
f64dc27f22bda11d945df314ec18d4bbac1e865b50212a45c0cf1ba3f3b5d21f
|
| 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 15, 2026.
Transparency logRelease files / depccg-3.0.0-cp313-cp313-macosx_11_0_arm64.whl
| Download URL | depccg-3.0.0-cp313-cp313-macosx_11_0_arm64.whl |
|---|---|
| Size | 951.2 kB |
| Tags | CPython 3.13 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
c071638cb06153a865c7d6a276a1a9c93a154571791857a7b463b0c5766c948e
|
|
BLAKE2b-256 checksum How to use checksums |
5070da57834d8dbbaaae1e7594549a59a3aedb6d9a77ec360019762447df7af3
|
| 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 15, 2026.
Transparency logRelease files / depccg-3.0.0-cp312-cp312-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
| Download URL | depccg-3.0.0-cp312-cp312-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl |
|---|---|
| Size | 1.7 MB |
| Tags | CPython 3.12 Linux glibc 2.27+ x86-64 Linux glibc 2.28+ x86-64 |
|
SHA-256 checksum How to use checksums |
9ac023f79dc319dd6281db544de6081d284077828c42ec3c05366bfc78abcf48
|
|
BLAKE2b-256 checksum How to use checksums |
645fd9f4fa9827059d1a10956fe71f3fa4477949275b373c076fdf2f4274425c
|
| 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 15, 2026.
Transparency logRelease files / depccg-3.0.0-cp312-cp312-manylinux_2_27_aarch64.manylinux_2_28_aarch64.whl
| Download URL | depccg-3.0.0-cp312-cp312-manylinux_2_27_aarch64.manylinux_2_28_aarch64.whl |
|---|---|
| Size | 1.7 MB |
| Tags | CPython 3.12 Linux glibc 2.27+ ARM64 Linux glibc 2.28+ ARM64 |
|
SHA-256 checksum How to use checksums |
7c24fe59b355e1956693c447494da641ed9f3592a41021cac1632b55a75b2484
|
|
BLAKE2b-256 checksum How to use checksums |
4dd8f11c0144d97572d893d08bcff7f065750c23c3b864551c33670ec0c3b967
|
| 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 15, 2026.
Transparency logRelease files / depccg-3.0.0-cp312-cp312-macosx_11_0_arm64.whl
| Download URL | depccg-3.0.0-cp312-cp312-macosx_11_0_arm64.whl |
|---|---|
| Size | 953.0 kB |
| Tags | CPython 3.12 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
822b4ffd19cb3991a27ad8a75dbe1b02373edc66bfee9021c9b0f6849b66e79e
|
|
BLAKE2b-256 checksum How to use checksums |
ac97c53dde0ec76343f9757f91b9673ebb74b074bbf770fc87d33c43c0323721
|
| 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 15, 2026.
Transparency logRelease files / depccg-3.0.0-cp312-cp312-macosx_10_13_x86_64.whl
| Download URL | depccg-3.0.0-cp312-cp312-macosx_10_13_x86_64.whl |
|---|---|
| Size | 944.5 kB |
| Tags | CPython 3.12 macOS 10.13+ x86-64 |
|
SHA-256 checksum How to use checksums |
d9051847fab615865bde54a18351842e8338a0b7984f604b5455e8a05e87b9b7
|
|
BLAKE2b-256 checksum How to use checksums |
9e6028ee8abd12b7f78e8470487bb8a088a8a3536a96748554a908cdbd0c694f
|
| 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 15, 2026.
Transparency logRelease files / depccg-3.0.0-cp311-cp311-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
| Download URL | depccg-3.0.0-cp311-cp311-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl |
|---|---|
| Size | 1.7 MB |
| Tags | CPython 3.11 Linux glibc 2.27+ x86-64 Linux glibc 2.28+ x86-64 |
|
SHA-256 checksum How to use checksums |
d35f3674457e77b667e6d0edb9c8faade5dbc4802ec81cb5281a3777969b5192
|
|
BLAKE2b-256 checksum How to use checksums |
0c0d527f90a96b75c1fd1538cd3437e1e8d9a8019b23e181b2f809cefa62397c
|
| 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 15, 2026.
Transparency logRelease files / depccg-3.0.0-cp311-cp311-manylinux_2_27_aarch64.manylinux_2_28_aarch64.whl
| Download URL | depccg-3.0.0-cp311-cp311-manylinux_2_27_aarch64.manylinux_2_28_aarch64.whl |
|---|---|
| Size | 1.7 MB |
| Tags | CPython 3.11 Linux glibc 2.27+ ARM64 Linux glibc 2.28+ ARM64 |
|
SHA-256 checksum How to use checksums |
47053c80f2a67f9a92e4c8e05e4b509d07456d017daef94262587aae65b2131b
|
|
BLAKE2b-256 checksum How to use checksums |
7ab2959d69b795502c127c5d66465670539e9bf1f63370f210ae32f9b39b6e3c
|
| 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 15, 2026.
Transparency logRelease files / depccg-3.0.0-cp311-cp311-macosx_11_0_arm64.whl
| Download URL | depccg-3.0.0-cp311-cp311-macosx_11_0_arm64.whl |
|---|---|
| Size | 951.5 kB |
| Tags | CPython 3.11 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
a364dc6aef006a92c14700311120d4a583bb1cc72ceee48c72d70e9f32592fc5
|
|
BLAKE2b-256 checksum How to use checksums |
916fae8629176b756d84df2df554691b469924062af48f8a3bfcb26f5603e0da
|
| 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 15, 2026.
Transparency logRelease files / depccg-3.0.0-cp311-cp311-macosx_10_9_x86_64.whl
| Download URL | depccg-3.0.0-cp311-cp311-macosx_10_9_x86_64.whl |
|---|---|
| Size | 942.6 kB |
| Tags | CPython 3.11 macOS 10.9+ x86-64 |
|
SHA-256 checksum How to use checksums |
f46eb7afa459b817358c29ca0eff0988528925b5cbad2bc23f0b1704d9d58374
|
|
BLAKE2b-256 checksum How to use checksums |
4b6f804f2fe3e48736d8a447e035d15cbb591ad830ac6061dbc431b7adf4b864
|
| 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 15, 2026.
Transparency logRelease files / depccg-3.0.0-cp310-cp310-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
| Download URL | depccg-3.0.0-cp310-cp310-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl |
|---|---|
| Size | 1.7 MB |
| Tags | CPython 3.10 Linux glibc 2.27+ x86-64 Linux glibc 2.28+ x86-64 |
|
SHA-256 checksum How to use checksums |
d87ea35b38673d003ca5c3bdfaa160e8690ba508de1dcaa9614d96305bee17d3
|
|
BLAKE2b-256 checksum How to use checksums |
67c41d04f3e495b436190b4e0a463b53418a8ac50f2774be570c54f115fc9cac
|
| 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 15, 2026.
Transparency logRelease files / depccg-3.0.0-cp310-cp310-manylinux_2_27_aarch64.manylinux_2_28_aarch64.whl
| Download URL | depccg-3.0.0-cp310-cp310-manylinux_2_27_aarch64.manylinux_2_28_aarch64.whl |
|---|---|
| Size | 1.7 MB |
| Tags | CPython 3.10 Linux glibc 2.27+ ARM64 Linux glibc 2.28+ ARM64 |
|
SHA-256 checksum How to use checksums |
e359d721a48b8e403a8d46abf0612813747db73655720cf9f5cbbea3d3829596
|
|
BLAKE2b-256 checksum How to use checksums |
14efa3be79494825d415dc44180012b73ffefc16006db372c48c072c6e41f6a7
|
| 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 15, 2026.
Transparency logRelease files / depccg-3.0.0-cp310-cp310-macosx_11_0_arm64.whl
| Download URL | depccg-3.0.0-cp310-cp310-macosx_11_0_arm64.whl |
|---|---|
| Size | 952.5 kB |
| Tags | CPython 3.10 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
94723b70e807c453f6fa5dc80defa7a81901d0b9781db7b66f9565842e0423cd
|
|
BLAKE2b-256 checksum How to use checksums |
905056cf1ec4a3bc2c4173c225a084e97ccbe76e56171652a984c318b00f0a56
|
| 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 15, 2026.
Transparency logRelease files / depccg-3.0.0-cp310-cp310-macosx_10_9_x86_64.whl
| Download URL | depccg-3.0.0-cp310-cp310-macosx_10_9_x86_64.whl |
|---|---|
| Size | 943.2 kB |
| Tags | CPython 3.10 macOS 10.9+ x86-64 |
|
SHA-256 checksum How to use checksums |
2ffa770ce86d14f68db0d885a39300b4172bcda0d048ff8a1034a807b4d4c488
|
|
BLAKE2b-256 checksum How to use checksums |
53ad1f4d8a3993c3745e716251ae37d675b7713c7b92bb767380b72b0c05dcc0
|
| 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 15, 2026.
Transparency logSecurity for depccg 3.0.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 19 files in this release have been uploaded with provenance metadata.
Attestation for depccg-3.0.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 15, 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.