Skip to content

AIWG 2026.8.26 - Verified dependency evidence

Choose a tag to compare

View all tags
@jmagly jmagly released this 27 Aug 02:42
· 36 commits to main since this release
v2026.8.26
This tag was signed with the committer’s verified signature.
jmagly Joseph Magly
GPG key ID: 839584D0E25E5126
Verified
Learn about vigilant mode.
4510694
This commit was signed with the committer’s verified signature.
jmagly Joseph Magly
GPG key ID: 454C68C4A2174CE9
Verified
Learn about vigilant mode.

AIWG 2026.8.26 - Verified dependency evidence

Release date: 2026-08-26

Channel: stable

AIWG 2026.8.26 strengthens two connected security boundaries: the dependency
graphs that enter a release and the evidence attached to alerts about those
graphs. Root, Droid Bridge, evaluation, and Tauri XML dependencies move to
patched releases, while exported findings become reproducible from an exact
commit and lockfile rather than relying on a package name alone.

What this changes for you

Patched dependency graphs with boundary tests

The root package now resolves patched nanoid and esbuild releases. Droid
Bridge upgrades its MCP and nested HTTP stack, with a real stdio initialization
test proving the bridge still completes the protocol handshake. Evaluation
tooling upgrades js-yaml and esbuild, with representative YAML parsing and
unsafe-tag rejection tests.

The Tauri build graph also moves to quick-xml 0.41.0, clearing the two
reported XML denial-of-service advisories. The desktop application does not
accept XML or plist input at its own boundary, but the safe minimum is now
documented and locked anyway.

Alerts identify the artifact that produced them

Dependency-alert exports now record the commit, workspace, manifest, lockfile
and its SHA-256 digest, dependency path, ecosystem, direct/transitive status,
and artifact-integrity evidence. The exporter rejects duplicate explicit alert
identifiers, advisories without usable identifiers or URLs, and patched-version
claims that do not match the affected dependency line.

That makes an alert answer the practical questions immediately: which artifact
was scanned, how did the package enter it, and can another reviewer reproduce
the result?

Obfuscation findings need behavioral evidence

Code that merely looks compressed or obfuscated is no longer enough for an
actionable security finding. Behavioral alerts must include a file, symbol,
rule identifier, confidence, artifact hash, and an excerpt or execution trace.
Review suppressions are tied to that exact hash and require a rationale, so a
changed artifact is reviewed again.

Package matrix

aiwg@2026.8.26
@aiwg/cli@2026.8.26
@aiwg/cockpit@2026.8.26

Upgrade

Run aiwg refresh to update through the installation method recorded for the
current machine and redeploy installed frameworks. Keep all three managed
packages on 2026.8.26. Source checkouts should update through their normal Git
workflow, build, and then run aiwg refresh --skip-update.

Rollback

Pin aiwg, @aiwg/cli, and @aiwg/cockpit to 2026.8.25 with the same
package manager used for installation, then run aiwg regenerate so deployed
provider context matches the restored version.

Release boundaries

  • The optional Tauri GTK3 source graph still contains glib 0.18.5, tracked by
    RUSTSEC-2024-0429 and roctinam/aiwg#2203. The issue is deferred until a
    compatible GTK4/Tauri release can be qualified; the advisory is not waived.
  • This release does not qualify or publish Linux .deb, .rpm, or .AppImage
    desktop bundles. Cockpit remains available through its Bridge-hosted browser
    UI and VS Code shell, and the npm package continues to ship the desktop source.
  • Exact-hash suppressions apply only to the reviewed artifact. Any content
    change produces a new hash and requires fresh review.
Assets 10
Loading