Repository navigation
Anti-REA Forge v1.1.0
Anti-REA Forge 1.1.0 — Verified REA disclosure boundaries
Released 2026-11-18. Python core and JavaScript SDK both use version 1.1.0.
This release closes demonstrated information-disclosure paths with real REA
controls, supported private-metadata separation and bounded key inspection.
It does not claim that distributed algorithms cannot be reconstructed.
Measured changes
| Control | Before / original | After / public | Restoration or compatibility control |
|---|---|---|---|
| REA + WABT private Wasm identifiers | 3 recovered | 0 recovered | Restored private original: all 3 recovered |
| Wasm executable content | 255-byte original | 134-byte public module | Every standard section byte unchanged; 9 numerical results identical |
| REA source-map original text | 1 exact original recovered | 0 exact originals recovered | Private map restored: 1 exact original recovered; JS byte identity retained |
| Five recoverable key representations | v1.0 allows all 5; recovered keys decrypt or sign | v1.1 positively detects and rejects all 5 | Public JWK and ciphertext without its external key both remain accepted |
Both Wasm and source-map controls run against published REA 6.9.0 and an
exact clean source build of c338e54c33213ca8dd157d30fbc922b65a04c49b. These have
separate runtime identities and reports. Official WABT 1.0.42 asset and executable
hashes are checked. The source build's commit, tree, lock file, build tools and
complete dist inventory are recorded and checked before and after execution.
Errors, missing tools and incomplete analysis fail the control.
Three private identifiers belong to one owned module; this is not three
independent attacks or a general success-rate estimate. Readable arithmetic WAT
remains present in every group. The five key controls use standard decoders and
cryptography rather than an REA agent session.
What changed
WebAssembly metadata and private originals
Default portable inspection recognizes bounded core-v1 Wasm envelopes by magic,
including renamed files and inspected ZIP/ASAR members. It rejects supported
private name, .debug_*, .zdebug_*, sourceMappingURL and
external_debug_info custom sections. Malformed envelopes, unsupported versions,
ambiguous private sections and exceeded budgets receive an explicit failure.
The new command:
mkdir public-wasm private-wasm
python -m releaseguard split-wasm-debug \
--input build/pricing.wasm \
--public public-wasm/pricing.wasm \
--private private-wasm/pricing.original.wasmcreates two new files. The private file is the complete original module;
only the public file belongs in the release. All retained sections are compared
byte-for-byte, both outputs are read back, and failed creation or changed input
rolls back newly created files. Unknown custom sections are preserved. The
production scanner/splitter does not require Node or WABT and never executes the
input. Complete integration and limits
Decoded JSON and DER key disclosure
The same bounded JSON read now checks source maps and supported key material.
It inspects escaped strings, root-string documents, object property names, exact
configured 32-byte arrays and supported JWK private components. Public fields
cannot hide directly recoverable private components merely by being absent or
incorrect. Unknown expressions, split/derived keys and arbitrary encodings remain
outside this scope; no target JavaScript is evaluated.
Standalone unencrypted DER recognition first reads a small ASN.1 prefix and only
admits private-key-shaped candidates to a bounded decoder. Supported private keys
are rejected. Recognized oversized or uninspectable private structures fail
explicitly. Public-key DER, public JWK and certificates have compatibility controls.
Report fields never include secret values or decoded JSON property names.
Installation and publication
Fresh wheel and source installations must perform Wasm separation and decoded-key
rejection on all three operating systems. Real REA npm and pinned-source recovery
controls are mandatory in the existing 13-job release policy. Publication still
requires a successful exact main commit, clean installation evidence, exact asset
hashes and a verified draft upload before making the Release public.
Upgrade
- CLI/import names and existing v1 signed-document and policy formats remain the same.
check_native_metadata: truenow rejects recognized Wasm private metadata. Run the new splitter or change your build to stop emitting private sections, then test the actual application.check_private_keys: truenow checks the supported decoded JSON/JWK and DER representations. Supplyingasset_key_filesalso enables their decoded JSON checks even when generic private-key marker checks are disabled.- Reports add
structured_secrets_checked,der_private_keys_checkedandstructured_secret_scan_completed. Any positive or incomplete-recognition finding keeps the gate closed. - Keep the original module, private map, credentials and issuer materials outside all public archives and deployments. Splitting must happen before signing or hashing the released module.
Evidence and limits
- npm Wasm control
- pinned-source Wasm control
- npm source-map control
- pinned-source source-map control
- Five key recoveries and two nonsecret controls
- Capability review and explicit remaining gaps (中文)
Wasm framing checks do not validate all instruction/type semantics. Custom-section
introspection can change application behavior, so developers must test their
actual embedding. PYC, CIL and public JS/Wasm instructions remain analyzable;
authorized runtime memory remains observable. The trusted service/external-key
boundary is still necessary for secrets that must not be delivered to a client.
See SECURITY.md for the full threat model. Downloaded assets
include release-evidence.json, installation-report.json and SHA256SUMS, which
bind the published files to the final main-branch CI run.