chore(deps): cargo-deny ban on pandoc Rust crates (B-006 E) - #4452
Merged
Conversation
Ban pandoc and pandoc_ast in cargo-deny so any future linked binding fails the bans check.\n\nGate-Passed: kanon 0.1.0
forkwright
enabled auto-merge (squash)
June 9, 2026 01:55
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
B-006 Chunk E (B-012 acceptance #4). Bans the pandoc + pandoc_ast Rust crates via cargo-deny [bans] with WHY reasons, enforcing the GPL-clean subprocess boundary: aletheia invokes the pandoc binary as an external subprocess and must never link a GPL Haskell-FFI binding. cargo deny check bans passes on the current tree (no such crate present) and would fail if one were added. Config-only; audit.toml/osv-scanner.toml left unchanged (they only mirror advisory ignores). No legit deps (resvg/zip/etc.) affected.