This release is a pre-release and may not be stable for production use.
potato-peeling
Algorithms for the potato-peeling problem: find the largest-area convex polygon contained in a simple polygon (its convex skull).
A C++ library with Python bindings; JavaScript bindings (a native Node.js addon and WebAssembly) are planned.
Contents
Methods
The same functions, with the same names and guarantees, in every language.
| Function | Algorithm | Answer |
|---|---|---|
convex_skull |
approximate_convex_skull, then refine |
the general-purpose method: certified, typically within 0.5% of optimal; may improve between versions |
exact_convex_skull |
Chang & Yap (1986) | the exact optimum; practical up to a few dozen vertices |
mesh_convex_skull |
Aronov et al. (2011) | optimum among unions of triangles of P's constrained Delaunay triangulation, or of a triangulation you pass |
approximate_convex_skull |
Cabello et al. (2017) | randomised approximation, deterministic for a given seed |
refine |
local ascent (from the thesis) | improves any convex polygon inside P; never returns less than it was given |
vertex_convex_skull |
Fischer; Bautista-Santiago et al. | the largest convex polygon whose vertices are vertices of P |
upper_bound |
pivot, two-pivot and width bounds | a certified upper bound on the optimum's area |
Utilities: is_convex_subset, segment_in_polygon, triangulate, reflex_vertices, longest_segment.
Every answer is a convex polygon inside P, checked exactly before it is returned. Input is a simple polygon without holes, in either orientation; repeated and collinear vertices are removed.
Python
Python 3.10 or later.
Quick start
import potato_peeling as pp
p = [(0, 0), (6, 1), (8, 5), (4, 4), (2, 8)]
skull = pp.convex_skull(p) # fast, certified, close to optimal
float(skull.area) # 21.687
skull.coords # [(0.0, 0.0), (6.0, 1.0), (7.908..., 4.816...), ...]
best = pp.exact_convex_skull(p) # the optimum
best.area # Fraction(109, 5), i.e. 21.8
best.vertices # ((8, 5), (4/5, 16/5), (0, 0), (6, 1)) as Fractions
float(pp.upper_bound(p)) # 21.826: no convex polygon in P is larger
Inputs and results
Polygons may be given as sequences of (x, y) pairs (int, float, Fraction or Decimal), NumPy arrays of shape (n, 2), or objects with __geo_interface__ such as shapely polygons (exterior ring only). Floats are read exactly: 0.1 is the double nearest 0.1.
Results are exact: a Skull has vertices and area as Fractions, coords as floats, and __geo_interface__, so shapely.geometry.shape(skull) works. Options are keyword arguments, for example pp.approximate_convex_skull(p, epsilon=0.05, seed=1).
Long runs and errors
Every method takes timeout= in seconds, which raises TimeoutError, and cancel=, a threading.Event or a callable checked about every 20 ms, which raises potato_peeling.Cancelled once set or true. refine, and convex_skull while refining, return the best answer so far instead. Ctrl-C interrupts any call on the main thread. Calls release the GIL, so polygons can be solved in parallel with threads; threads= additionally parallelises Cabello's step (0, the default, uses every core).
InvalidPolygonError (a ValueError) is raised for input that is not a simple polygon; CertificationError if a result fails its own check, which would be a bug.
C++
C++17, on CGAL's exact kernel.
Quick start
#include <iostream>
#include <potato_peeling/potato_peeling.hpp>
namespace pp = potato_peeling;
int main() {
// A CGAL::Polygon_2 over CGAL's exact kernel (Epeck): a simple polygon,
// either orientation, with exact coordinates.
pp::Polygon p;
for (auto [x, y] : {std::pair{0, 0}, {6, 1}, {8, 5}, {4, 4}, {2, 8}})
p.push_back(pp::Point(x, y));
const pp::Skull skull = pp::convex_skull(p); // fast, certified
const pp::Skull best = pp::exact_convex_skull(p); // the optimum
std::cout << CGAL::to_double(skull.area) << " " << best.area << " "
<< pp::upper_bound(p) << "\n"; // 21.6869 21.8 21.8256
}
A Skull holds the polygon (counter-clockwise, without collinear vertices) and its exact area. Each method also accepts a CGAL::Polygon_2 over any other CGAL kernel, and takes an options struct as its last argument: BaseOptions for exact_convex_skull, mesh_convex_skull and vertex_convex_skull, and for the others ConvexSkullOptions, ApproximateOptions, RefineOptions or UpperBoundOptions, which extend it.
Without CGAL
potato_peeling/simple.hpp offers the same methods on plain double coordinates and includes no CGAL headers; results are the exact answers rounded to nearest.
#include <potato_peeling/simple.hpp>
namespace ps = potato_peeling::simple;
const ps::Ring p{{0, 0}, {6, 1}, {8, 5}, {4, 4}, {2, 8}};
const ps::SimpleSkull skull = ps::convex_skull(p); // skull.polygon, skull.area
Using it with CMake
The library builds as a shared library with a CMake package:
find_package(potato_peeling CONFIG REQUIRED)
target_link_libraries(app PRIVATE potato_peeling::potato_peeling)
Errors and cancellation
Methods throw invalid_polygon (a std::invalid_argument) for input that is not a simple polygon, and certification_error if a result fails its own check, which would be a bug. BaseOptions, and so every options struct, has a should_stop callback, called between units of work; when it returns true the method throws cancelled, except refine, which returns its answer so far.
Building
Requires a C++17 compiler, CMake 3.20 or later, and the CGAL (5.4 or later), Boost (1.74 or later), GMP and MPFR development packages. CDT is used if installed, otherwise a pinned release is downloaded during the build.
Python package:
uv sync
C++ library and its tests:
cmake -S . -B build -DCMAKE_BUILD_TYPE=Release
cmake --build build
cmake --install build --prefix <prefix>
Tests
uv run pytest # Python, ~2 min; -m slow for the larger set
ctest --test-dir build -LE slow # C++, ~30 s; -L slow for the brute-force sweeps
The Python tests check the exact methods against the exact optima published in the thesis, on 81 Natural Earth polygons (tests/data/optima.json), and every method's guarantees on those and on hand-made polygons. The C++ tests check the vertex skull, longest segment and mesh skull against brute-force searches on random polygons.
Background
The implementations were developed for the thesis Peeling Potatoes Exactly and Almost Exactly: Computing the Convex Skull of a Polygon (Zane Dmitri Pereira, The University of Melbourne, 2026). The code and results as used in the thesis are archived in potatoes-research; this library has since been reworked (no GPL dependencies, a new API, bug fixes), so its approximate answers can differ from the thesis's, while its exact answers match.
Licence
LGPL-3.0-or-later; see COPYING.LESSER and COPYING. Only the LGPL-licensed parts of CGAL are used; the build defines CGAL_LICENSE_ERROR, so including a GPL-licensed CGAL package fails to compile.
Third-party licences and notices are in THIRD-PARTY-NOTICES.txt and LICENSES/.
Built on CGAL, the Computational Geometry Algorithms Library. If you use this library in published work, please also cite CGAL: The CGAL Project. CGAL User and Reference Manual. CGAL Editorial Board. https://doc.cgal.org (how to cite).
Metadata
Release files for potato-peeling 0.1.0a3
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 | Actions |
|---|---|---|---|---|
| potato_peeling-0.1.0a3.tar.gz | 260.9 kB | With provenance | Details for potato_peeling-0.1.0a3.tar.gz |
Built distributions (wheels)
Total release size: 17.0 MB
Release files / potato_peeling-0.1.0a3.tar.gz
| Download URL | potato_peeling-0.1.0a3.tar.gz |
|---|---|
| Size | 260.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
8681ff1b9ce39e6ecc7b6dedadae5c152111423ea5eb6e67fe5e08633e510f73
|
|
BLAKE2b-256 checksum How to use checksums |
d993e73ac8f4d21a2f43e8e724f52c99e9f8048c660d2110580a17164bc91b27
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 12, 2026.
Transparency logRelease files / potato_peeling-0.1.0a3-cp312-abi3-win_amd64.whl
| Download URL | potato_peeling-0.1.0a3-cp312-abi3-win_amd64.whl |
|---|---|
| Size | 1.2 MB |
| Tags | CPython 3.12 Windows x86-64 abi3 |
|
SHA-256 checksum How to use checksums |
0ea731c5188f2532c7a4444e62fb804c7fdf1d470f4031bec204a7f11eeafd79
|
|
BLAKE2b-256 checksum How to use checksums |
ad6ebfa0c697f12d6d66cbbf38af8cf5d24371fa2dbb7d4141c242023a1a2341
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 12, 2026.
Transparency logRelease files / potato_peeling-0.1.0a3-cp312-abi3-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
| Download URL | potato_peeling-0.1.0a3-cp312-abi3-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl |
|---|---|
| Size | 1.3 MB |
| Tags | CPython 3.12 Linux glibc 2.27+ x86-64 Linux glibc 2.28+ x86-64 abi3 |
|
SHA-256 checksum How to use checksums |
e5521b2c82ce3bc321587b6f214d0be5b27770c03e63f1b346a86711f17d58c2
|
|
BLAKE2b-256 checksum How to use checksums |
871f137456dc7a84dcc5060eab59f2750b70c8c330f460764127e8ce043ab61c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 12, 2026.
Transparency logRelease files / potato_peeling-0.1.0a3-cp312-abi3-manylinux_2_26_aarch64.manylinux_2_28_aarch64.whl
| Download URL | potato_peeling-0.1.0a3-cp312-abi3-manylinux_2_26_aarch64.manylinux_2_28_aarch64.whl |
|---|---|
| Size | 1.1 MB |
| Tags | CPython 3.12 Linux glibc 2.26+ ARM64 Linux glibc 2.28+ ARM64 abi3 |
|
SHA-256 checksum How to use checksums |
b04a30143020c12edbe00d5e79a77147705965ae741937b4f745e4f4c5a0f1e2
|
|
BLAKE2b-256 checksum How to use checksums |
12ef08bc9645422a6e3fd7964fd5dd076c86b44da9115fac8054aa1487593670
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 12, 2026.
Transparency logRelease files / potato_peeling-0.1.0a3-cp312-abi3-macosx_11_0_x86_64.whl
| Download URL | potato_peeling-0.1.0a3-cp312-abi3-macosx_11_0_x86_64.whl |
|---|---|
| Size | 1.1 MB |
| Tags | CPython 3.12 abi3 macOS 11.0+ x86-64 |
|
SHA-256 checksum How to use checksums |
0a9ad6c6a4aad405928daba9cf69b68dd7ab17193af0a6dc23c3a892c3dc233d
|
|
BLAKE2b-256 checksum How to use checksums |
cea5b9eec0c6de20ba4a9c97167c4e6435752d4194eb4d684219a1628342681a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 12, 2026.
Transparency logRelease files / potato_peeling-0.1.0a3-cp312-abi3-macosx_11_0_arm64.whl
| Download URL | potato_peeling-0.1.0a3-cp312-abi3-macosx_11_0_arm64.whl |
|---|---|
| Size | 933.0 kB |
| Tags | CPython 3.12 abi3 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
4e532773e5cd2f9bf5d4b6aea5465d90103ab4b82186ab7e237b171c2b271403
|
|
BLAKE2b-256 checksum How to use checksums |
ae778a692c0285ebc60d8077fc2cab4de6104d67b33d724ffaed9d18dfbe52fc
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 12, 2026.
Transparency logRelease files / potato_peeling-0.1.0a3-cp311-cp311-win_amd64.whl
| Download URL | potato_peeling-0.1.0a3-cp311-cp311-win_amd64.whl |
|---|---|
| Size | 1.2 MB |
| Tags | CPython 3.11 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
84b8e1e7aceaf6694e9ec76ab7d21e45e7bf6aaed1c0974ed506b29a6e4f1775
|
|
BLAKE2b-256 checksum How to use checksums |
b2f08af2da04a8babef9588b44ac0fd648158215305153e65921140738afd3fb
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 12, 2026.
Transparency logRelease files / potato_peeling-0.1.0a3-cp311-cp311-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
| Download URL | potato_peeling-0.1.0a3-cp311-cp311-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl |
|---|---|
| Size | 1.3 MB |
| Tags | CPython 3.11 Linux glibc 2.27+ x86-64 Linux glibc 2.28+ x86-64 |
|
SHA-256 checksum How to use checksums |
a8642ffe1a24e2a60dd655f35df3cd4c46f3ad0b1058319592297ceb9bdf9c1b
|
|
BLAKE2b-256 checksum How to use checksums |
bea54466373adf4123cfd39fa536478fdee94d7bca16079c538ae3eeb0d0a5b9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 12, 2026.
Transparency logRelease files / potato_peeling-0.1.0a3-cp311-cp311-manylinux_2_26_aarch64.manylinux_2_28_aarch64.whl
| Download URL | potato_peeling-0.1.0a3-cp311-cp311-manylinux_2_26_aarch64.manylinux_2_28_aarch64.whl |
|---|---|
| Size | 1.1 MB |
| Tags | CPython 3.11 Linux glibc 2.26+ ARM64 Linux glibc 2.28+ ARM64 |
|
SHA-256 checksum How to use checksums |
1d5c84390d7f96e7c9bb3f1a7a45a7cd3f11c553ca5e85188f3f5a9464613c95
|
|
BLAKE2b-256 checksum How to use checksums |
e0f973c9dc41ce76b8475f62fa2678bb0cdc1269d40fc4e530335f430c9546e2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 12, 2026.
Transparency logRelease files / potato_peeling-0.1.0a3-cp311-cp311-macosx_11_0_x86_64.whl
| Download URL | potato_peeling-0.1.0a3-cp311-cp311-macosx_11_0_x86_64.whl |
|---|---|
| Size | 1.1 MB |
| Tags | CPython 3.11 macOS 11.0+ x86-64 |
|
SHA-256 checksum How to use checksums |
b2784fd006e9cddce8d83784498f0376d92fe7b5c0eab2e77aecbc021e027630
|
|
BLAKE2b-256 checksum How to use checksums |
88ddbf4f522326ffb7617a81cc1891c193eaf95ca4e19da4b433cd15147f957b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 12, 2026.
Transparency logRelease files / potato_peeling-0.1.0a3-cp311-cp311-macosx_11_0_arm64.whl
| Download URL | potato_peeling-0.1.0a3-cp311-cp311-macosx_11_0_arm64.whl |
|---|---|
| Size | 934.8 kB |
| Tags | CPython 3.11 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
9965aa7b84c074b259c0f8a89e9392d8869f3ce5d5b6291e7c6e39c90ae5b5aa
|
|
BLAKE2b-256 checksum How to use checksums |
cf607959926dce442d27d2994b7aceb1334c244627e4b5b737e2e4b98d719311
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 12, 2026.
Transparency logRelease files / potato_peeling-0.1.0a3-cp310-cp310-win_amd64.whl
| Download URL | potato_peeling-0.1.0a3-cp310-cp310-win_amd64.whl |
|---|---|
| Size | 1.2 MB |
| Tags | CPython 3.10 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
ec2d80b1a87b587ea95ba3ea2531c0a7d89c12ce8972e8dc7df9bd1837ec3e3b
|
|
BLAKE2b-256 checksum How to use checksums |
23d26b5f71b5ad62bfcdb27d1ae5425b73978edad8ab38940a8ebfcd97fc6e74
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 12, 2026.
Transparency logRelease files / potato_peeling-0.1.0a3-cp310-cp310-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
| Download URL | potato_peeling-0.1.0a3-cp310-cp310-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl |
|---|---|
| Size | 1.3 MB |
| Tags | CPython 3.10 Linux glibc 2.27+ x86-64 Linux glibc 2.28+ x86-64 |
|
SHA-256 checksum How to use checksums |
9dc3ead57c4403622bcc3a097d5f1cb6a8af593eacb0fd81b963bcded874c72d
|
|
BLAKE2b-256 checksum How to use checksums |
3f4d112af6bdf6ca5e3b4d0a960ae99d3b11b6051b5f1c7d22ed249501292ef7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 12, 2026.
Transparency logRelease files / potato_peeling-0.1.0a3-cp310-cp310-manylinux_2_26_aarch64.manylinux_2_28_aarch64.whl
| Download URL | potato_peeling-0.1.0a3-cp310-cp310-manylinux_2_26_aarch64.manylinux_2_28_aarch64.whl |
|---|---|
| Size | 1.1 MB |
| Tags | CPython 3.10 Linux glibc 2.26+ ARM64 Linux glibc 2.28+ ARM64 |
|
SHA-256 checksum How to use checksums |
b1ed9ee1b88dd08e088f61e7f1b3b68ee40b6d3cf1c4c48c78d34f1d1cfe6fd5
|
|
BLAKE2b-256 checksum How to use checksums |
3dae7947639dd10996fa72459fc1753254aae3cf8be876150213c3d0aa816214
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 12, 2026.
Transparency logRelease files / potato_peeling-0.1.0a3-cp310-cp310-macosx_11_0_x86_64.whl
| Download URL | potato_peeling-0.1.0a3-cp310-cp310-macosx_11_0_x86_64.whl |
|---|---|
| Size | 1.1 MB |
| Tags | CPython 3.10 macOS 11.0+ x86-64 |
|
SHA-256 checksum How to use checksums |
8f38d0a62ec7fe08176774e117279669b11799d85423354d4836346fe13d2a1d
|
|
BLAKE2b-256 checksum How to use checksums |
5d377a577fc1c08b5d0eac77a60e841b5c0192d78a2c874994299ff61e162258
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 12, 2026.
Transparency logRelease files / potato_peeling-0.1.0a3-cp310-cp310-macosx_11_0_arm64.whl
| Download URL | potato_peeling-0.1.0a3-cp310-cp310-macosx_11_0_arm64.whl |
|---|---|
| Size | 934.9 kB |
| Tags | CPython 3.10 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
1ac1f39b1d3148a0ee9777bda642382b5f245b259ba90e8297f80c576103db8b
|
|
BLAKE2b-256 checksum How to use checksums |
09f2f6840f90b17ebec698d16d80085627f0583fa50de37025a8ec1a671859fd
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 12, 2026.
Transparency logSecurity for potato-peeling 0.1.0a3
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.
Attestation for potato_peeling-0.1.0a3.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 Nov 12, 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.