everydeck-check
The everydeck check for app repositories. It validates everydeck/everydeck-befund.json with everydeck's own rules, finds everydeck calls that went missing from the code, re-anchors places that moved and publishes the facts to everydeck. It never sends code.
pip install everydeck-check
everydeck-check validate everydeck/everydeck-befund.json --repo .
Commands:
validate <befund> [--repo .]: the check everydeck runs when a Befund is submitted (shape, references, result signal, derived manifest), plus building blocks of the repository that must appear incoverage[].drift <befund> --repo . [--freeze]: is every everydeck call still in the code (againsteverydeck-manifest.lock.json);--freezewrites the lock file.reanchor <befund> --repo .: moves every place of the Befund from its commit to HEAD (git diff, text, symbol); nothing is guessed, unresolved places are listed.reads <befund>: the cross-check of display locations.publish <befund> --url <everydeck> --project <id>andchange: send the facts to everydeck.
everydeck's rules ship inside the package (everydeck_check/rules/everydeck-rules.mjs) and run with node (18 or newer). Python 3.11 or newer. License: MIT.
1 maintainer
Metadata
1 maintainer
Release files for everydeck-check 0.2.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 | |
|---|---|---|---|---|
| everydeck_check-0.2.0.tar.gz | 164.1 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| everydeck_check-0.2.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 334.3 kB
Release files / everydeck_check-0.2.0.tar.gz
| Download URL | everydeck_check-0.2.0.tar.gz |
|---|---|
| Size | 164.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e1f5af842d89ae3ccb8e54806ffd1dd227490f23281d32be5df28de03b683fa1
|
|
BLAKE2b-256 checksum How to use checksums |
c59c9828cf185609fc185485433a57fdcb2aec52143e461d802ce14566dab132
|
| 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 Oct 12, 2026.
Transparency logRelease files / everydeck_check-0.2.0-py3-none-any.whl
| Download URL | everydeck_check-0.2.0-py3-none-any.whl |
|---|---|
| Size | 170.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
a55e3395cb4c214d436e3c080ab32c16d23b714601abdef2d0c13618f826e144
|
|
BLAKE2b-256 checksum How to use checksums |
885caf5995d108d806fbd702586baa88951fe2cc9c9ac35fd06f8731b89398e3
|
| 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 Oct 12, 2026.
Transparency logSecurity for everydeck-check 0.2.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 2 files in this release have been uploaded with provenance metadata.
Attestation for everydeck_check-0.2.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 Oct 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.
