Skip to content

Anti-REA Forge v1.4.0

Latest

Choose a tag to compare

@github-actions github-actions released this 18 Nov 08:41
4a39c52

Anti-REA Forge 1.4.0 — Complete-content protection and clearer workflows

Release date: 2026-11-18. Python core and JavaScript SDK use 1.4.0.
The existing v1 signed-document formats, CLI/import names and default JSON protocol
remain compatible. This release adds no runtime dependency to the SDK.

Version 1.4 closes two publication gaps reproduced against the official v1.3.0
wheel and makes protection references easier to configure and diagnose. A release
gate controls what is shipped; distributed code and disclosed keys remain readable
by REA and other independent consumers.

Measured improvements

Control Official v1.3.0 Version 1.4.0 Evidence
Complete private source with a prefix, suffix or concatenated bundle Allows all three wrappers Positively rejects all three Both real REA distributions identify the owned function and its constants; a recovered module produces the same four results
Locating value crossing a 128 KiB window Allows the containing file Rejects with a completed content check Separate position control, not an additional vulnerability
Wrapped content in six ZIP/ASAR layouts Allows all six deployments Rejects all six Disk, nested members and verified unpacked siblings share the production decision; layouts are not added to REA recovery counts
Six supported keys inside JSON strings Allows all six usable keys Positively detects all six Real Node JSON.parse plus Ed25519 signatures or AES-256-GCM decryption
Six recoverable over-budget or ambiguous JSON inputs Allows all six Refuses all six as incomplete inspection Kept separate from positive key findings
Six normal structured-data controls Allows all six Allows all six Includes public JWK, ordinary text, a 1.1 MiB string and 260 empty container placeholders
Initialize with private/key references Flags are unavailable Validates and saves configuration-relative paths Zero manual configuration edits; a moved project works through the real CLI and Node SDK
Explain one exact-copy finding 74 lines / 4,695 characters of JSON 23 lines / 1,026 characters of text, with a next action One fixed report: 68.92% fewer lines; not a scanning-speed or general usability score

The content controls use npm REA 6.9.0 and a separately built source tree at
675287517c98c702ee88ad036c5e3b8dd4bcc7a7. These are actual deterministic CLI
providers, not an autonomous model session. Key and workflow controls use real
standard consumers and do not invoke REA. All fixtures are owned, synthetic inputs.

Records: content / npm,
content / source,
stringified keys,
workflow,
full assessment.

Complete private contents inside larger payloads

Existing private_input_files references now use exact-content/v1 automatically.
The complete unchanged bytes can appear anywhere inside an inspected physical file,
ZIP/ASAR member or validated unpacked sibling. Adding a build header, trailing newline
or concatenated public module no longer avoids the check.

References retain their limits: at most 64 files, 1 byte to 8 MiB each, 64 MiB total.
A prefix of at most 64 bytes locates a long candidate, then its entire original length
is verified with SHA-256. Short references match their complete bytes, including
one-byte references; common short values can therefore match ordinary public content.
Duplicate references share work while preserving rule indices.

The whole release shares 4,096 candidate checks / 512 MiB of candidate verification
reads
, in addition to existing release/container limits. Exhaustion produces
private_input_unverifiable and private_input_scan_completed: false; it never
becomes a successful absence result. New reports include the profile, checked payload
count, candidate count and charged verification bytes. Contained positives retain
private_input_exposure and add representation: "contained-bytes".

Snapshots and reports do not expose external reference paths, locating bytes, contents
or separate reference hashes. Public file/member paths and public inventory hashes
remain visible. prepare retains its scan-to-sign input rechecks and rollback on a
failed final verification. See full profile.

Stringified JSON keys with shared limits

The structured-secret scanner parses at most two additional JSON-string container
layers along a nested path
, then uses the existing private JWK, PEM/DER and known-key
rules. Each container is limited to 64 KiB UTF-8 text. All branches and DER/PEM
decodes share 64 candidates / 256 KiB, and all parsed nodes count toward the
100,000-node / 64-depth limits.

Recognizable overdeep/oversized containers, duplicate members and nonfinite numbers
fail as incomplete inspection. Ordinary text and obvious templates skip the parser.
Syntactically empty objects, arrays and empty quoted strings need no parse and consume
no decode budget. Nonempty public containers still count: 65 serialized public objects
can exceed this bounded profile even without private material.

Positive nested findings have a fixed json-stringified-... representation and
stringified_layers count. Decoded values, field names and key digests are absent
from the findings. No JavaScript evaluation or arbitrary encoding recursion is added.

Configure once and understand failures

Use matching 1.4.0 core and SDK archives from this release:

python -m pip install --upgrade https://github.com/Afloat16/anti-rea-forge/releases/download/v1.4.0/open_release_guard-1.4.0-py3-none-any.whl
npm install https://github.com/Afloat16/anti-rea-forge/releases/download/v1.4.0/anti-rea-forge-releaseguard-1.4.0.tgz

For a new configuration, supply the protection inputs that exist in your project:

python -m releaseguard project-init --root dist --product MyApp --out .releaseguard \
  --private-input-file service/private_quote.py --asset-key-file issuer/asset.key
python -m releaseguard check --config .releaseguard/project.json --format text

Both reference flags are repeatable. Omit whichever kind your product does not use.
Inputs must already exist; dist may be built later. Initialization validates inputs
before writing, saves paths relative to project.json, rechecks them after writing,
and removes a new configuration bundle if final validation fails. Existing config
directories are not overwritten. Existing configurations require no schema migration;
edit their private build configuration only when adding references.

scan-release, check and prepare accept --format text. Reports show configured
reference counts, enabled/completed inspections, public locations, rules and fixed
remediation actions. Zero references are explicitly marked not configured.
Dynamic strings use escaped JSON-style quoting, including control and Bidi characters.

JSON remains the default, and --format json is explicit. Exit codes remain 0
(configured checks pass), 3 (publication blocked by findings), 2 (operation
error) and 130 (cancelled). Failures retain stdout/stderr separation. prepare
sidecars remain JSON with the existing signature format. The SDK keeps the machine
protocol and does not acquire a signing or authorization-issuance method.

Validation and publication

Local validation ran 1,066 Python test cases: 1,065 passed and 1 skipped, plus
10 test classes skipped during setup for unavailable platform/compiler dependencies.
The unittest summary therefore contains 11 skip records; setup-class skips are not
subtracted again from the executed-case total. The SDK passed 67 tests and 12 real
CLI integrations
. The change adds 65 Python test methods. Skips are recorded and
not counted as successes. Validation record

The required CI set remains 13 jobs across Linux, Windows and macOS, including
real LLVM 18, Ghidra, REA npm/source, official ASAR, native compilers and fresh package
installations. New content, key and workflow controls are mandatory in the existing
REA job. Fresh wheel/sdist must enforce containment, stringified-key rejection, saved
references and readable reports; the packed SDK must enforce containment and saved
references. The publisher requires each relevant installation flag to be strictly true.

Public assets include the wheel, source archive, SDK archive, SHA256SUMS,
installation-report.json and release-evidence.json. Publication binds successful
CI and installed artifact checks to the exact main commit and archive hashes.

Remaining boundaries

The changed-comment source fixture deliberately remains allowed and REA-recoverable:
complete unchanged reference bytes are absent even though its function behaves the
same. Rewrites, minification, compilation, encoding, fragments, undeclared private
files and arbitrary application secrets remain outside the content profile. Keep
private service implementations out of public build inputs; this scanner does not
automatically partition an application.

The matching resource probe is a local bounded-work measurement, not a total process
memory or general throughput guarantee. Trusted build paths, stable staging files,
external keys and independently enforced service authorization remain required.
Existing historical recovery failures remain published. The release does not claim
that REA, another file reader or an authorized runtime can no longer analyze software.