Repository navigation
Release/v1.6.0 - #50
Merged
Merged
Conversation
…xpansion 1.1.21 and 5.0.12, source-map-js 1.2.2, @types/node 22.20.5, tsx 4.23.15, typescript-eslint 8.72.1 Closes Dependabot alerts 18-26 (all development scope) and supersedes the Dependabot pull requests 43-49; the lockfile is regenerated with npm 11.19.1. npm audit --audit-level=high reports none; the remaining moderate advisory (minimatch < 11.0.1, GHSA-g3hv-75wg-m249, 2026-10-30) has no fix inside the eslint 9 / typescript-eslint 8 lines and is development-only.
… eol-lf now fails Every tracked text blob is LF, as .gitattributes (`* text=auto eol=lf`) has declared since 1.5.0. Nothing but carriage returns changed (16 547 bytes removed); verify:docs rule eol-lf is an error from this commit on (EOL_LF_MODE = 'fail'), and the sample baseline entry of attachments/01-pdfa3-with-xml, which embeds invoice.xml byte for byte, is re-anchored in the v1.6.0 rebaseline (compatibility ledger).
…ctual-text, five Indic scripts, spot colours, the PDF/A-2 + PDF/X-4 dual claim, JPEG 2000, four diagnostics, --on-stream-error The lockfile resolves pdfnative 1.9.0 (the ^1.8.0 range is unchanged; the pin and the engine-surface matrix move in a later commit). The bridge gains the 1.9.0 block; the --font allow-list adds gu, pa, kn, ml, or (32 scripts, 36 modules); render gains --direction auto|ltr|rtl and --actual-text, drops the --pdfx × --tagged pre-check (the engine's pdfa1b/pdfa3b refusals are E_INPUT), documents spot colours and JPEG 2000, and lists the four 1.9.0 diagnostics (13); the envelope carries tagged, direction and actualText. extract-text and compare take --on-stream-error limit|throw|skip and map PdfStreamLimitError to E_INPUT by instance. The it.fails markers for Khmer, Myanmar and CJK untagged extraction are gone (fixed upstream); the build-error fixture is the 1.9.0 registry (33 messages); JPEG 2000 fixtures come from the engine's helpers; a multilang sample renders the five scripts. verify:docs leaves a shipped release note out of the count-checked corpus once its tag exists and the CHANGELOG has an [Unreleased] entry.
…s /Link body, decodePdfTextString from the engine
ltv embed takes --cert <pem|der>, --ocsp <der>, --crl <der> (repeatable) and
--match all|chain next to --data: the /DSS data is composed by pdfnative
1.9.0's composeLtvData() from files on disk, without any network; the two
inputs are exclusive, a composeLtvData refusal is E_INPUT, the envelope
carries match. annotate's link entries go through the engine's
buildAnnotationBody({ type: 'link' }) (#91) after validateURL — the CLI no
longer writes a PDF dictionary of its own. inspect and compare decode /Info
text strings with the engine's decodePdfTextString() (#85); the decoder the
CLI carried since 1.5.0 is removed.
…synthetic profiles from pdfnative/tools tests/regression/engine-surface.json maps every bullet of the engine's 1.9.0 changelog entry (72) to named CLI tests or a motivated waiver; the suites it names are new: render-direction (UAX #9, /ActualText on right-to-left runs, the opt-out), render-spot-colours (/Separation, /DeviceN + /Colorants, the engine's refusals as E_INPUT, ChartSeries.colors under PDF/X-4), render-images (JPEG 2000 pass-through, /SMaskInData, the two PDF/A diagnostics), render-engine-1-9 (subset tag, lean and compact subsets, the .notdef stub, one text object per line, the transparency group, tagged-table semantics, U+202F on base-14, the paginated table of contents, the amount column, a label-less chart series) and two fuzz regressions (CWE-835 tokenizer, CWE-125 font parser). The synthetic Gray and CMYK profiles come from pdfnative/tools (byte-identical to the committed copies); the vendored generator is gone and scripts/lib/icc-canary.ts patches the ICC version bytes for the PDF/A-1 canary. The deep-descender fix (#80) is a tested-upstream waiver: a CLI document table row already clears the descender.
…EG 2000, one rebaseline; --variant table guards infoItems; version 1.6.0 Eight samples join the corpus (five Indic scripts, --direction auto, spot colours under PDF/X-4, the PDF/A-2b + PDF/X-4 dual claim, a JPEG 2000 image, per-bar chart colours, a 160-entry table of contents, ltv embed from offline material) with their dual-shell pairs; the conformance corpus gains the dual claim (claims: both, counted by veraPDF and validatePdfX), spot colours under PDF/X-4 and a JPEG 2000 pair (PDF/A-2b positive, PDF/A-1b negative canary). The sample baseline is re-anchored once at 1.6.0 — 36 moved, 8 added, the semantic projection now records the /DSS inventory — with the causes in its provenance. The table-variant sample carried infoItems as strings: pdfnative 1.9.0 throws on them where 1.8.0 rendered "undefined", so render --variant table refuses that shape (and a malformed row) with E_INPUT before the engine, and the schema documents the typed shape. release-prepare set the version to 1.6.0 (the release note is scaffolded; the narrative follows).
…ndomness) CodeQL #16/#17 traced the Math.random() entropy of the tests' temp-file names into the owner password a command received (utils/layout.ts), a finding on the CLI for a cause in the tests. tests/helpers/cli-harness.ts gains tmpName(name) on node:crypto randomUUID; TempFiles.path() and the eighteen local tmp() helpers use it. tests/tools/workflows.test.ts will hold the tree to it.
…d→build→publish→attest, compat-previous and ClusterFuzzLite The CI/CD alignment with pdfnative 1.9.0, held by tests/tools/workflows.test.ts: - ci.yml: no path filter; one gate job spanning ci (22), ci (24), windows and macos (name = the required context), compat-previous (the v1.5.0 suite against the current src/, tag fetched anonymously) and workflow lint (zizmor 1.30.1, actionlint 1.7.12 by checksum). .github/rulesets/main.json requires the seven contexts and allows a merge commit next to squash (.git-blame-ignore-revs). - codeql.yml: job-level permissions, actions + javascript-typescript, build-mode none, security-extended (Scorecard #2). Every checkout on 7.0.1, every codeql-action on 4.38.0, harden-runner audit reasons dated. - publish.yml: guard (tag only) → build (publish gate, one tarball with its digests) → publish (installs nothing, npm 11.19.1 pinned by SHA-512, OIDC) → attest (the registry bytes, three SBOMs, Sigstore bundle on the release); setup-verapdf hands its directory back as an output (zizmor github-env). SLSA Build L2, stated as such (Scorecard #14/#15). - node-current.yml (Node 26, advisory), fuzz.yml (ClusterFuzzLite, advisory), dependabot.yml with a seven-day cooldown on four ecosystems. - scripts/run-compat.ts + tests/compat/allow-1.5.0.json (each exclusion with a reason and its ledger entry); tests/compat/{manifest,status,subjects}-1.5.0.json captured from [email protected] and held by tests/tools/manifest-compat.test.ts (a 1.x minor only adds); gate step compat:previous (publish profile). - fuzz/: nine targets over the CLI's own parsers through #fuzz-surface (fuzz/surface.ts, bundled with the engine by tsup into fuzz/.build/ for the container, aliased to the source under vitest); parseConfigText and parseFetchUrl are the pure halves the targets needed; Jazzer.js pinned by lockfile under .clusterfuzzlite/engine/, never in package.json; tests/fuzz/targets.test.ts runs the seeded, truncated and mutated corpus and proves every target rethrows a planted engine error. - verify-docs reads the include matrix (ciMatrixMajors) and allows the advisory newer major; SECURITY.md gains §Supported runtimes and §Compatibility promise; CONTRIBUTING.md, scripts/README.md, the testing instructions and the agent files describe the seven checks, compat:previous and the fuzz targets. 1539 tests, 102 test files.
…map, changelog, security, citation, keywords; the release note and the baseline provenance - README: the v1.6.0 banner and SEO sentence, two highlights, the v1.6.0 feature-table group, the 26-file corpus status, the Node/OS requirements (Bun and Deno are not tested), a v1.6.0 quick start, the render/ltv/extract-text/compare/annotate references, the agent section's compatibility promise, the four-job supply chain, the native family links. - KNOWLEDGE_BASE: the 1.9.0 bridge block, direction/spot/dual-claim/JPX section, the four diagnostics, extract-text/ltv/annotate updates, nine API-mapping rows, the tree (run-compat, fuzz/, .clusterfuzzlite/, tests/compat/), the samples table, two FAQ entries, the dev reference (compat:previous, targets.test.ts). - AGENT_CONTRACT: four status fields, the stream-limit and logical-order notes, the offline LTV rung, the stable-across-1.x safety note. llms.txt follows. - ROADMAP: the v1.6.0 block; spot colours and the dual claim delivered, the Thai tone-mark limit, the compatibility snapshots and the ICC version option recorded. - CHANGELOG: [1.6.0] – 2026-10-31 with the ltv/annotate/inspect, compatibility, CI/CD and security entries; compare link. - package.json description and keywords (116 → 146: right-to-left, the five scripts, JPEG 2000, spot colours, the dual claim, ltv-offline, backward-compatible, fuzz-tested, …); CITATION.cff abstract and keywords; the release-audit skill's blind spots; copilot and AGENTS pointers. - release-notes/v1.6.0.md written (ledger C1–C5, the rebaseline groups, the verification figures the publish gate will confirm); the baseline provenance says 46 re-anchored + 8 added, as the diff against v1.5.0 shows.
…findings; no JPX canary under PDF/A-1 - ltv: a PEM bundle is recognised anywhere in the file (openssl -text and PKCS#12 preambles), a document the engine cannot read during composeLtvData is E_PARSE with its message (mapPdfError) instead of a bare E_RUNTIME, and collect/add refuse the embed-only --cert/--ocsp/--crl/--match flags instead of ignoring the material. - extract-text/compare: the --on-stream-error remedy is named only by the two commands that own the flag (mapPdfError's streamErrorFlag); every other command names --max-inflate-size. - render: the envelope's tagged is emitted for a PDF/A level only, as schema status types it (a --layout "tagged": true never reaches it). - config: a read failure of the config file reports the I/O error, not "invalid JSON". - run-compat/gate/ci/publish: one allow-list discovery in numeric order (allow-1.10.0 after allow-1.9.0) shared by the gate and the workflows; --tag runs under that release's own allow-list or exits 2; a malformed allow-list fails the step with the file named. - corpus: the jpx-pdfa1b negative canary is removed — veraPDF 1.30.2 accepts /JPXDecode under PDF/A-1b, so "must reject" was a false expectation; the engine's PDFA1_JPX_IMAGE diagnostic stays held by the diagnostics suite. 25 corpus files (20 PDF/A, 6 PDF/X). - tests: run-compat.test.ts (discovery order, --tag allow-list, the allow-list contract), three ltv cases, one render envelope case. 1554 tests, 103 files.
A buffered render and its streamed twin rendered in consecutive calls can straddle a second boundary, and then differ in /CreationDate alone: a flake, not a parity failure (seen once under a coverage run, never under the gate). Both tests pin --creation-date.
…erage 86.86 % statements Measured on the release branch: the publish gate (veraPDF 1.30.2, the v1.5.0 suite replayed) 15 passed, 0 skipped in 424 s; coverage 86.86 / 77.37 / 92.73 / 88.48; validate:pdfa 16 PASS + 4 XFAIL; verify:docs 26 rules. coverageMeasured follows the note.
…dual claim; the PR body for v1.6.0 The independent verification before this PR found that `inspect --check pdfa,pdfx` — the form the release note, the README, the knowledge base, the render usage text and the shipped print/09-dual-pdfa2b-pdfx4 scripts use — was refused with exit 2: only the repeated form was accepted. --check now splits on commas (additive; a trailing comma is an empty value, refused as before), with a test; the docs name both forms. Also: the ltv refusal message agrees in number, and the note says which schema subject lists the 13 diagnostic codes. release-notes/draft/PR-v1.6.0.md holds the verification table and the human-in-the-loop steps. 1555 tests.
…the second audit pass release-prepare --date 2026-11-01 re-stamps the manifest, the three Verified-on stamps and CITATION.cff; CHANGELOG, the release note and ROADMAP by hand. Ledger C2 now says the over-cap inflate error reaches every command that opens a PDF (E_PARSE -> E_INPUT, verify excepted); C6 records the table-variant guard; C1-C4 are the allow-list entries, C5-C6 repository-side. ecosystem.json: pdfnative-mcp 1.7.0, pdfnative-react 1.3.0. AGENT_CONTRACT and llms.txt name the --check comma list and the dual claim. Four ROADMAP items from the audit (verify --password, E_IO for ENOENT, inspect --check before the read, typed manifest flags). The PR draft carries the 18-finding ledger of the second pass and the upstream alignment contents.
…notate-link built at runtime The five JPEG 2000 fixtures were binary only by git's NUL heuristic; the rule makes it explicit (blobs unchanged, no renormalisation). A literal U+0000 in annotate-link.test.ts made the file a binary blob for git, invisible to the eol-lf rule and to grep -I; the probe URL is now built with String.fromCharCode(0), as the testing rules ask.
Dependency ReviewThe following issues were found:
|
|
You are seeing this message because GitHub Code Scanning has recently been set up for this repository, or this pull request contains the workflow file for the Code Scanning tool. What Enabling Code Scanning Means:
For more information about GitHub Code Scanning, check out the documentation. |
There was a problem hiding this comment.
CodeQL found more than 20 potential problems in the proposed changes. Check the Files changed tab for more details.
…dings on the release PR CodeQL js/file-system-race: readBinaryFileCapped sized a file with stat() and re-opened it by path; it now opens one descriptor, takes the size from it and reads at most that many bytes (a file swapped or grown after the check still lands capped). CodeQL js/insecure-temporary-file: the suites created files with guessable names straight under os.tmpdir(), a flow CodeQL followed into writeOutput; tmpName() now hands out paths under a private mkdtemp directory (mode 0700, removed at exit, extension kept) and every suite uses it — no path.join(os.tmpdir(), ...) is left in tests/; the fuzz manifest suite gets a mkdtemp directory of its own. Dependency Review: BlueOak-1.0.0 (tar, minipass, yallist, chownr, isexe) and CC-BY-4.0 (caniuse-lite) reach the tree only through .clusterfuzzlite/engine/package-lock.json, never through package.json; both are allow-listed with the reason, the workflows test pins the list. The testing instructions and the generated rule state the temp-file convention; the release note, CHANGELOG and PR draft record the findings.
…o /tmp literal handed to a command, an anchored veraPDF-host assertion js/insecure-temporary-file still reached writeOutput through two '/tmp/…' literals (render --watch usage test, the mocked writeOutput unit test) and readBinaryFileCapped's open() through a suite's own mkdtemp directory; every temp directory of the suites is now created under tmpRoot() (tests/helpers/cli-harness.ts), the harness holding the only os.tmpdir() call in the tree, and the two literals are a tmpName() path and a relative path. js/regex/missing-regexp-anchor: the workflows assertion on the veraPDF download host is a substring check. The testing instructions, the generated rule, the release note, CHANGELOG and PR draft follow.
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
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.
v1.6.0 — right-to-left, 32 scripts, spot colours & the dual PDF/A + PDF/X claim
Summary
Aligns the CLI with pdfnative 1.9.0 in both directions. Every 1.9.0 engine feature is
exposed: right-to-left layout under the full UAX #9 (
render --direction auto|ltr|rtl,--actual-text), five more Indic scripts (gu pa kn ml or— 32 Unicode scripts, 36 fontmodules), spot colours (
layout.print.spotColours,{ spot, tint }/{ inks }values),the PDF/A-2 + PDF/X-4 dual claim in one file, JPEG 2000 images, four more diagnostics, the
stream-limit policy of
extractText()(extract-text/compare --on-stream-error),offline LTV material (
ltv embed --cert/--ocsp/--crl --match), engine-built/Linkbodiesand text-string decoding. Every roadmap item the engine unblocked is delivered: logical-order
extraction of untagged shaped text, the paginating table of contents, label-less chart
series, the dual claim, spot colours.
For an agent: the command surface is 100 % backward-compatible and now proved so — the
v1.5.0 test suite and its
schema manifest/status/listcaptures run against thecurrent sources on every pull request (
compat-previous,tests/compat/), SECURITY.mdstates the compatibility promise and the supported runtimes, and every new envelope field
(
tagged,direction,actualText,match) is pinned byschema status.For the repository: the CI/CD is aligned with the engine's — the gate required on Ubuntu
(Node 22, 24), Windows and macOS,
workflow lint(zizmor + actionlint), CodeQLsecurity-extendedwith theactionslanguage,publish.ymlas guard → build → publish →attest (npm client pinned by SHA-512, the registry bytes attested, SLSA Build L2),
ClusterFuzzLite over nine parser targets, Dependabot with a cooldown, a repository
normalised to LF, and every open Dependabot and code-scanning item of the backlog closed or
acknowledged (below).
Counts: 21 commands, 19 schema subjects, 12 stable error codes, 10 global flags and 14
manifest commands unchanged;
renderflags 57 → 59;extract-text9 → 10;compare8 → 9;
ltv7 → 11;--font27 → 32 scripts (36 modules);--strictdiagnostics 9 → 13;doctorchecks 8 (unchanged); sample baseline 91 → 99 PDFs; conformance corpus 22 → 25files; workflows 9 → 11; tests 1403 → 1555 across 103 files (was 96); npm keywords
116 → 146.
Changes
Engine surface (
src/core-bridge/index.ts,src/commands/render.ts,src/utils/)(pdfnative 1.9.0):PdfStreamLimitError,decodePdfTextString,composeLtvData,ocspResponseMatchesCertificate, the typesTextDirection,SpotColourDef,PdfSpotColor,PdfInkMix,StreamErrorPolicy,LtvMaterial,ComposeLtvOptions,LinkMarkupAnnotation;buildSyntheticGrayProfile/buildSyntheticCmykProfilefrompdfnative/tools.utils/layout.ts:VALID_DIRECTIONS,--direction→layout.direction,--actual-text→
layout.actualText; the--pdfx × --taggedpre-check removed (the engine decides perlevel).
utils/fonts.ts: five Noto modules (36 / 32).utils/build-errors.ts: theSpot colour …/Ink mix …prefixes.utils/pdfops.ts:parseStreamErrorPolicy,PdfStreamLimitError→E_INPUTby instance, the--on-stream-errorremedy named only bythe commands that own the flag.
utils/pdftext.tsdeleted (engine decoder).utils/config.ts:parseConfigText(pure half, fuzzed);utils/fetch-guard.ts:parseFetchUrl(admission half, fuzzed); an unreadable config file reports its I/O error.commands/render.ts:conformanceFieldsaddstagged(a PDF/A level only),direction,actualText: false;assertTableParamsShaperefuses a malformedPdfParamswithE_INPUT.Commands
render:--direction,--actual-text;gu pa kn ml or; spot colours (JSON); the dualclaim; JPEG 2000 pass-through;
PDFA_GLYPH_WITHOUT_UNICODE,PDFA1_JPX_IMAGE,PDFA_JPX_IMAGE,TEXT_GLYPH_NOT_COVEREDunder--strict; envelopetagged,direction,actualText.extract-text/compare:--on-stream-error limit|throw|skip; logical-order text fromuntagged shaped and right-to-left runs.
ltv embed:--cert/--ocsp/--crl(repeatable, PEM anywhere in the file or DER,16 MiB each),
--match all|chain, exclusive with--data;composeLtvData:refusals →E_INPUT, an unreadable document →E_PARSEwith its message;collect/addrefusethe embed-only flags; envelope
match.annotate:linkbodies frombuildAnnotationBody({ type: 'link' });parseAnnotationsJsonexported for the fuzz target.inspect/compare:/Infostringsthrough
decodePdfTextString.schema:statuspins the four fields;renderdescribes direction, actualText, spotcolours, JPEG 2000, the dual claim, the table-variant shape; 13 diagnostics, 32 scripts.
completion: every new flag.index.ts: usage texts.Tooling (
scripts/)run-compat.ts(npm run compat:previous): the previous release'stests/,samples/and vitest config at its tag, the current
src//scripts//dist/beside them, thesuite minus
tests/compat/allow-<version>.json(reason + ledger entry per exclusion;--tagruns under that release's own allow-list; a malformed list exits 2 with the filenamed).
gate.ts: stepcompat:previous(publish profile; one allow-list discovery sharedwith
run-compat.ts, numeric order).lib/pdfa-corpus.ts:Claim = 'pdfa' | 'pdfx' | 'both' | 'none',claimsStandard;entries
pdfx4-spot-colours,dual-pdfa2b-pdfx4(both),jpx-pdfa2b(25 files).lib/icc-canary.tsreplaces the vendoredsynthetic-gray-profile.ts(the profiles comefrom
pdfnative/tools).lib/sample-plan.ts,generators/derived.ts(
sign/rsa-pkcs7-ltv-offline.pdf),lib/sample-fingerprint.ts(the/DSSinventory inthe semantic projection).
verify-docs.ts: the include-form CI matrix (ciMatrixMajors), the advisory newer major,a shipped release note leaving the count-checked corpus,
eol-lfas an error.CI / repository (
.github/, root)ci.yml(no path filter;ci (22),ci (24),windows,macos,compat-previous,workflow lint),codeql.yml(job-level permissions,actions+javascript-typescript,build-mode none,
security-extended),publish.yml(guard → build → publish → attest),node-current.yml(Node 26, advisory),fuzz.yml(ClusterFuzzLite, advisory), the othersix on checkout 7.0.1 / codeql-action 4.38.0 with dated harden-runner reasons;
setup-verapdfreturns an output.dependabot.yml(four ecosystems, 7-day cooldown).rulesets/main.json(seven required contexts;merge+squash).fuzz/(nine targets,surface.ts,_contract.js),.clusterfuzzlite/(project.yaml,digest-pinned Dockerfile, build.sh,
engine/with Jazzer.js 4.0.0 pinned by its ownlockfile),
tsup.config.ts(the fuzz surface bundle intofuzz/.build/, git-ignored),vitest.config.ts(the#fuzz-surfacealias),package.jsonimports(private),tsconfig.test.jsonpaths..git-blame-ignore-revs,EOL_LF_MODE = 'fail');tests/helpers/cli-harness.tstmpName()onrandomUUID(); dev toolchain patch(vitest 4.1.12, vite 8.3.5, brace-expansion, source-map-js,
@types/node, tsx,typescript-eslint);
package.jsondescription + keywords;CITATION.cff.Agent layer
docs/AGENT_CONTRACT.md(four status fields, the stream-limit and logical-order notes, theoffline LTV rung, "stable across 1.x"),
llms.txt,AGENTS.md/CLAUDE.md(compat,fuzz/,fuzz/.build/never read, the publish gate's compat step),.github/instructions/(commands, testing: compat + fuzz rules) →
.claude/rules/,copilot-instructions.md,.claude/skills/release-audit/SKILL.md(two blind spots),.claude/settings.json(
Read(fuzz/.build/**)denied).Samples and tests
render/multilang/12-five-indic-scripts,13-rtl-direction,render/print/08-spot-colours,09-dual-pdfa2b-pdfx4(+ pairs),render/images/01-jpeg2000(+
minimal-rgb.jp2),render/chart/06-per-bar-colours,render/toc/02-long-toc,extract-text/03-rtl-logical-order(pair),sign/11-ltv-offline(pair);table-variant/01-financial-transactions.jsoncorrected to{ label, value }.re-anchored to
since: 1.6.0(every sample embedding a font — lean, compact, taggedsubsets —, every untagged document with shaped or RTL text —
/ActualText—, one textobject per line, the watermark transparency group, tagged-table semantics, the engine's
/Linkbody,invoice.xmlnormalised to LF, the corrected table variant; the encrypted andsigned semantic entries follow their subsets) and 8 added; 45 keep their 1.5.0 reference.
render-direction,render-spot-colours,render-images,render-engine-1-9,tests/fuzz/targets(the ClusterFuzzLite targets),tests/fuzz/pdf-bytes(stream limit, CWE-835) andfonts(CWE-125),tests/tools/ manifest-compat,run-compat,synthetic-profiles,workflows(rewritten), the ltvoffline-material cases,
tests/regression/engine-surface.jsonat 72 items (engine 1.9.0),tests/fixtures/pdfnative-build-errors.jsonat 33 messages, JP2 fixtures.Documentation
requirements and supported OSes, quick start, command reference for render / ltv /
extract-text / compare / annotate, agents, security, related projects),
docs/KNOWLEDGE_BASE.md,docs/AGENT_CONTRACT.md,llms.txt,SECURITY.md(§Supportedruntimes, §Compatibility promise, §Code Safety, §Supply chain + Scorecard),
CONTRIBUTING.md(gate, compat, fuzzing, SHA resolution, release steps, branch protection),
ROADMAP.md(v1.6.0 block; the future list re-triaged),
CHANGELOG.md(1.6.0 + compare link),scripts/README.md,samples/README.md,tests/fixtures/README.md,release-notes/v1.6.0.md.GitHub backlog
@vitest/mocker×2)caed1ac); all development scope, none shipped@types/node, tsx, typescript-eslint), #48, #49js/insecure-randomness)6fad8d1: onetmpName()onrandomUUID())security-events: write)codeql.yml, job level)npm install -g npm@…unpinned)contents: writein publish)attestjob's only write grant, release assets)npm audit --audit-level=highclean (one moderate, unfixable in the eslint 9 line, documented)fuzz.yml,fuzz/,.clusterfuzzlite/)js/file-system-race(src/utils/io.ts),js/insecure-temporary-file(io.ts+ the suites) andjs/regex/missing-regexp-anchor(workflows.test.ts), firstsecurity-extendedrun on this PRreadBinaryFileCappedsizes and reads through one descriptor; every test temp file comes fromtmpName()and every temp directory frommkdtempundertmpRoot()(the harness holds the onlyos.tmpdir()call in the tree), the two/tmpliterals handed towriteOutputare gone; the veraPDF-host assertion is a substring check.clusterfuzzlite/engine/package-lock.jsondependency-review.ymlwith the reason (fuzzing engine only, never in the package; BlueOak-1.0.0 is OSI-approved)Independent audit
/release-audit release-notes/v1.6.0.md v1.5.0— pending, run by the maintainer (theskill is reserved for explicit user invocation). In its place, before this PR, an independent
verification agent (fresh context, the built binary, the
schemaoutputs, the v1.5.0captures, targeted suites, greps with line numbers) ran 28 checks:
--helpandschema manifest;schema statuspinstagged,direction,actualText,match; the right-to-left recipe extracts both source strings inlogical order; the dual claim renders with
tagged+pdfxin the envelope andpdfa1bisE_INPUT;--on-stream-error bogusis exit 2;ltv add --certis refused namingltv embed; the table-variant guard;doctor36 / 32;verify:docs26 rules; nothing removedfrom completion.ts / error.ts / schema.ts since v1.5.0 and the counts 57→59, 9→10, 8→9,
7→11;
manifest-compatgreen;actualText: falseonly when switched off; the PEM preamble;the 33-message fixture; the one remaining
it.fails).inspect --check pdfa,pdfx, the form the note, the README, theknowledge base, the render usage text and the shipped
print/09-dual-pdfa2b-pdfx4.{sh,ps1}use, was refused with exit 2 (only the repeated form was accepted). Fixed in this branch:
--checktakes a comma list (additive), with a test; the docs name both forms.implied
schema renderlists the 13 diagnostic codes (fixed:schema statusdoes).compat:previous, the coverage figures, thepublish gate and veraPDF — all run by the author, figures below.
Second pass (2026-11-01, the publish day) — two independent auditors (internal
conformance; engine coverage, breaking changes and state of the art) and an adversarial
verifier that reproduced every piece of evidence itself. 18 findings, none blocking: 14
legitimate or partial, 3 rejected, 1 unverifiable offline. Every retained finding is applied
on this branch.
release-prepare --date; CHANGELOG, the note and ROADMAP by hand); the 14 harden-runner reasons keep their decision dateverifyexcepted)undefined :in 1.5.0, E_INPUT now) had no ledger entryecosystem.jsonquoted pdfnative-mcp 1.6.0 (newest tag v1.7.0); no pdfnative-react entry*.jp2/*.j2k binaryrule (five fixtures binary by git's heuristic only).gitattributesextended, no renormalisationannotate-link.test.tsa binary blob for git (invisible toeol-lf)String.fromCharCode(0)--checkmissing from AGENT_CONTRACT / llms.txt, and a stale "PDF/X and PDF/A cannot be claimed by the same file" sentenceengine-surface.json$commentsaid "every bullet"; the test takes bold-titled bullets, the engine's five Documentation bullets are outside$commentrewordedverifyon an encrypted file is E_PARSE (inspect: E_PASSWORD), no--password--inputis E_RUNTIME with a raw ENOENT, not E_IOinspectwrites its artefact before refusing an invalid--checkschema manifestflags carry no type / enum / descriptionltv collect/addrefusing the embed-only flagsltvhad none of them)Holds re-checked by the verifier:
verify:docs26 rules, zero CRLF blob,npm pack --dry-run10 files, the full SHA in
.git-blame-ignore-revs,engine-surface.test.ts"maps everybullet" ran (10/10),
schema statuspins the four fields, noCo-Authored-Byin the branch.Before the audit,
/code-review highon the branch diff returned nine findings, all fixedin
e26c272(a PEM preamble longer than 64 bytes was handed to the engine as DER; anon-
composeLtvData:engine error lost its message;ltv collect/addignored thematerial flags; the
--on-stream-errorhint reached commands without the flag;tagged: truefrom a layout reached the envelope; the allow-list discovery was implemented threetimes with two orders;
--tagran under the wrong allow-list; a config read failure read as"invalid JSON"; a malformed allow-list crashed the gate's skip check).
Validation (what actually ran on the release branch, Windows 11, Node 22.23.2)
npx tsx scripts/gate.ts --fast→ typecheck:all, lint, test (1555 tests), verify:docs —all pass.
npm run test:coverage→ 1555 / 1555 passing across 103 files; coveragestatements 86.86 % / branches 77.37 % / functions 92.73 % / lines 88.48 % (thresholds
82 / 71 / 86 / 82, unchanged).
npm run verify:docs→ 26 rules across the documentation corpus, 0 errors, 0 warnings(
eol-lfis an error since the normalisation commit).npm run build && npm run test:generate && npx tsx scripts/verify-samples.ts --strict→99 sample PDFs match the baseline (88 byte-exact, 11 semantic).
npm run corpus:pdfa && npm run validate:pdfx→ 25 files; PDF/X 5 PASS + 1 XFAIL;npm run validate:pdfa(veraPDF 1.30.2, JDK 13) → 16 PASS + 4 XFAIL + 5 SKIP (thePDF/X-only files), exit 0 — the dual claim and the JPX under PDF/A-2b accepted.
npm run compat:previous(tagv1.5.0) → 67 files, 839 cases of the v1.5.0 suite greenagainst the current sources (14 exclusions, each with a reason; the exclusions reference
four ledger entries, C1–C4; C5 and C6 are repository-side changes outside the allow-list).
npx tsx scripts/gate.ts --publish --require-allat31e5cc3(re-run after the secondaudit pass, the date bump and the CodeQL / Dependency Review fixes; the earlier runs at
4e6ecaeand5bfee87were 15/15 in 374 s and 551 s) → 15 passed, 0 skipped in 1005 sunder load (typecheck:all 97 s, lint 28 s, build 38 s, dist-check, smoke 11 s — 21
commands —, bundle-size 381 KiB of the 448 KiB budget, bundle-check — 2 externals —,
test:generate 153 s — 99 PDFs —, test:coverage 221 s — 1555 tests, 86.9 % stmts —,
verify:docs 17 s, verify:samples 20 s, corpus:pdfa 50 s — the 25-file corpus —,
validate:pdfx 11 s, validate:pdfa 250 s — veraPDF 1.30.2, 16 PASS + 4 XFAIL —,
compat:previous 109 s — the v1.5.0 suite).
--version1.6.0;doctor --format json(pdfnative 1.9.0, fonts36 / 32, 13 conformance-relevant diagnostics listed by
schema); the quick-start recipesof the release note against
dist/cli.cjs;govern verify-issuegreen on the fourupstream drafts.
npm audit --audit-level=high→ clean.workflow lint,CodeQL's
actionsscan,fuzz.yml,node-current.ymlrun for the first time on this PR;publish.ymlon the release) — the audit verdict is conditional on that first green run.Backward compatibility
additive and pinned by
schema status; the v1.5.0schemacaptures are held bytests/tools/manifest-compat.test.ts.tests/compat/allow-1.5.0.json, release note §Compatibility):C1 the dual claim is accepted (the usage error is gone;
pdfa1b/pdfa3bkeep alevel-specific
E_INPUT); C2 a stream past--max-inflate-sizeisE_INPUTinextract-text/compare(--on-stream-error skiprestores the 1.5.0 answer); C3untagged shaped / RTL /
substext extracts as its source; C4 the inventory counts(36 / 32 modules / scripts, 13 diagnostics); C5
invoice.xmlis LF./ActualText, one textobject per line, transparency groups, tagged-table semantics) — spec-valid output, not
byte-identical to 1.5.0; one declared rebaseline.
Out of scope (tracked in ROADMAP.md)
metadatakeeping the PDF/X identification; reproducible signed output(per-revision
/ID); PDF/X-1a / -3 / -4p; a Thai above-vowel + tone-mark pair extractingin geometric order from untagged output (
it.fails thToneBelow); aversionoption on thesynthetic ICC builders;
buildPDFBytesvalidatinginfoItems— issue drafts under.github/drafts/(validated bygovern verify-issue), submitted by the maintainer.visual
compare(no rasteriser);optimize/ linearisation; category help commands; manpages; positional arguments in manifest tasks; a committed
manifest.jsonsnapshot and aJSON-LD /
llms-full.txtvariant (derivable fromschema manifest); a performance budget.Human-in-the-loop — steps for the maintainer
release/v1.6.0, open this PR with this body. The first run exercises the Windowsand macOS legs,
workflow lint, CodeQLactions,fuzz (code change)andnode 26forthe first time: expect to iterate on a first red there (the ruleset is not imported yet,
so a red leg does not block).
compat-previousneeds thev1.5.0tag on the remote(it is).
.github/rulesets/main.json(seven required contexts:ci (22),ci (24),windows,macos,compat-previous,workflow lint,sample-regression; merge methodsmerge+squash) — CONTRIBUTING §Branch protection.9b661b1(the LFnormalisation) listed in
.git-blame-ignore-revs; a squash would change the SHA toignore. Title
release: v1.6.0 — right-to-left, 32 scripts, spot colours & the dual PDF/A + PDF/X claim.v1.6.0on the merge commit, publish the GitHub Release (body =release-notes/v1.6.0.md);publish.ymlrefuses anything but that tag, re-runs thepublish gate, publishes through Trusted Publishing and attests the registry bytes. Approve
the
npm-publishenvironment when asked..github/drafts/to Nizoka/pdfnative, andthe alignment PR on the engine side —
docs/assets/ecosystem.json(pdfnative-cli 1.5.0 →1.6.0, pin
^1.9.0);docs/data/surfaces.jsonrowsspot-colours,images-jpeg2000,rtl-direction(CLI supported,render, since 1.6.0) and 1.6.0 notes on the LTV,text-extraction, annotate and PDF/X-4 rows;
docs/guides/cli.md(header, "9 codes" → 13,"27 script codes" → 32, the render table with
--direction/--actual-text/ JPEG 2000 /spot colours / the dual claim replacing "mutually exclusive",
--checkcomma list, the fourltvflags,--on-stream-errorunder extract-text and compare, the engine-built link body,"31 properties" → 35);
docs/guides/choose.md,docs/guides/use-cases-cli.md,README.md,llms.txtanddocs/index.htmlwhere they quote the CLI version; thennpm run verify:docsupstream.
project meets every criterion: README / CONTRIBUTING / MIT / CHANGELOG / semver tags;
rulesets and release notes; SECURITY.md with private reporting;
npm run gatewithenforced coverage thresholds; the engine's crypto, input validation and the SSRF guard;
Trusted Publishing with provenance; no medium+ vulnerability; CodeQL + ESLint;
ClusterFuzzLite + the hostile-input suites) and add the badge to the README comment slot;
set the GitHub topics (
pdfnative, cli, pdf, pdf-generation, json-to-pdf, pdf-a, pdf-x, pades, digital-signature, encryption, streaming, typescript, nodejs, zero-dependency, ai-agents, llms-txt, human-in-the-loop, unicode, right-to-left, reproducible-builds);git config blame.ignoreRevsFile .git-blame-ignore-revson each clone.Self-review checklist
release-notes/v1.6.0.mdand CHANGELOG §1.6.0 say the same things as this body.docs/assets/ecosystem.jsonholds every figure quoted;npm run verify:docsis green.Co-Authored-Bytrailer and no "Generated with" footer anywhere on the branch.fixcolumn filled(the maintainer's
/release-auditrun; the verification agent's table is above).