Skip to main content

everydeck-check

The everydeck check for app repositories. It validates everydeck/app-map.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/app-map.json --repo .

Commands:

  • The app map is everydeck/app-map.json; without a path the commands read it there (an earlier setup's everydeck/everydeck-befund.json is still read).
  • validate <app_map> [--repo .]: the check everydeck runs when an app map is submitted (shape, references, result signal, derived manifest), plus building blocks of the repository that must appear in coverage[].
  • drift <app_map> --repo . [--freeze]: is every everydeck call still in the code (against everydeck-manifest.lock.json); --freeze writes the lock file.
  • reanchor <app_map> --repo .: moves every place of the app map from its commit to HEAD (git diff, text, symbol); nothing is guessed, unresolved places are listed.
  • reads <app_map>: the cross-check of display locations.
  • footprint --base <commit before the setup> [--fix-lock]: the files the setup added and changed, a lockfile rewritten beyond the new packages (--fix-lock restores it with only the new packages) and leftovers such as .playwright-mcp/ or screenshots.
  • publish <app_map> --url <everydeck> --project <id> and change: 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.

Changes

0.3.2

  • validate derives people from the schema with the same rule as everydeck: the profile table (one row per account), people without a login (records with a person's name and an e-mail or phone, not money), memberships with a role.
  • A table without a known primary key is identified by its id column before any foreign key.
  • flow_candidates[].redirect on password_reset: the page of the app a password reset email leads to.
  • Amounts and limits are editable; locked for good are identifiers, references and owners (LOCKED_ROLES = ("ref", "person")).

Metadata

Release files for everydeck-check 0.3.2

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

Source distribution (sdist)

Source distribution for everydeck-check 0.3.2
File Size Uploaded Provenance
everydeck_check-0.3.2.tar.gz 172.6 kB With provenance Details

Built distribution (wheel)

Table of built distributions (wheels) for everydeck-check 0.3.2
File Interpreter ABI Platform
everydeck_check-0.3.2-py3-none-any.whl Python 3 none any Details

Total release size: 351.4 kB

Release files / everydeck_check-0.3.2.tar.gz

Download URL everydeck_check-0.3.2.tar.gz
Size 172.6 kB
Tags Source
SHA-256 checksum
How to use checksums
13c43c1bb6b034a21493a1b57a727597ded373528f85af0fa1e715c622d836bc
BLAKE2b-256 checksum
How to use checksums
113ef34bc39bce24b3c71947f7dc0d7427dd42f5a3d8e367a29636f81be8d7f4
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 16, 2026.

Transparency log

Release files / everydeck_check-0.3.2-py3-none-any.whl

Download URL everydeck_check-0.3.2-py3-none-any.whl
Size 178.8 kB
Tags Python 3
SHA-256 checksum
How to use checksums
034036e90c4f37977100c1ebdcec960ffa86c2e189b6d510f49c27ec4d0f3a7f
BLAKE2b-256 checksum
How to use checksums
927f92d5b716bc73f8575d6303a0a615115292037d727ea2df1c780fcacf43a4
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 16, 2026.

Transparency log

Security for everydeck-check 0.3.2

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

Full provenance

All 2 files in this release have been uploaded with provenance metadata.

Select from 2 files

Attestation for everydeck_check-0.3.2.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 16, 2026.

Transparency log

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

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

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