
Security News
GitHub to Block pull_request_target Workflows by Default Starting December 2
GitHub is tightening GitHub Actions security with new restrictions on privileged pull request workflows. Here's what changes and how maintainers are affected.
@algovoi/keystone-verifier
Advanced tools
Independent, offline, one-call verifier for AlgoVoi keystone evidence: re-derives a keystone record, a Payment Evidence Frame, an audit chain of frames, or a full bundle from raw fields and confirms every reference matches. Depends only on JCS RFC 8785 ca
Independent, offline, one-call verification of AlgoVoi keystone evidence.
Given a keystone record, a Payment Evidence Frame, an audit chain of frames, or a full bundle of
all three, this re-derives every content-addressed reference from the raw fields and confirms it
matches the carried value. It depends only on the substrate JCS canonicalisation (sha256_jcs),
not on the packages that produced the evidence, so an auditor verifies without trusting the
builder. RFC 8785 JCS + SHA-256 are the whole dependency; it runs on any substrate version (v0/v1).
pip install algovoi-keystone-verifier
from algovoi_keystone_verifier import verify_bundle, verify_keystone, verify_frame, verify_audit_chain
res = verify_bundle({
"keystone": keystone_record, # passport/mandate/policy/decision/execution/trust_query
"frames": [pef_frame, ...], # optional Payment Evidence Frames
"audit_chain": audit_chain, # optional chain of frames, capped
})
res.ok # True iff every re-derivation matched
res.to_dict() # {"ok": ..., "checks": [{"name","ok","detail"}, ...]}
It re-derives decision_ref, execution_ref, trust_query_ref and the chain; the PEF
receipt_hash and frame_id; the audit-chain rows (prev_hash linkage, genesis 64 zeros) and the
trust_query_ref cap; and cross-checks that frames carry the keystone's execution_ref. Tamper any
field and the relevant check fails.
CLI:
cat bundle.json | python -m algovoi_keystone_verifier # exit 0 if every check passes
TypeScript twin: @algovoi/keystone-verifier,
byte-identical re-derivation.
Apache-2.0. This open verifier checks the content-addressed references (the unsigned substrate). A commercial tier verifies the cryptographic signatures (hybrid Falcon-1024 + ML-DSA-65) and ingests into the Compliance Command Center.
Pinned edition for adopters, with a free key. Pin algovoi-keystone-verifier==0.1.0, anchor a
keystone_v1 (or pef_keystone_v1) vector hash, and keep the NOTICE; that four check gate earns a
free v0 licence key for algovoi-mandate-auditor (email chopmob@gmail.com with your import-by-hash
evidence and the NOTICE).
Python and TypeScript produce identical re-derivations. Redistribution must retain the NOTICE and
the Apache-2.0 LICENSE.
FAQs
Independent, offline, one-call verifier for AlgoVoi keystone evidence: re-derives a keystone record, a Payment Evidence Frame, an audit chain of frames, or a full bundle from raw fields and confirms every reference matches. Depends only on JCS RFC 8785 ca
We found that @algovoi/keystone-verifier demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 1 open source maintainer collaborating on the project.

Security News
GitHub is tightening GitHub Actions security with new restrictions on privileged pull request workflows. Here's what changes and how maintainers are affected.

Security News
/Application Security
A practical guide to securing GitHub Actions against supply chain attacks, covering malicious pull requests, credential theft, dependency risks, and release pipelines.

Security News
Composer 2.11 adds dependency cooldowns, joining package managers that delay new releases to reduce supply chain risks while allowing urgent security updates.