Skip to content

Agent Guard 1.1.1

Choose a tag to compare

View all tags
@VODuda VODuda released this 14 Nov 20:03
· 6 commits to main since this release
v1.1.1
d92c44f
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Agent Guard 1.1.1

A documentation-only patch of @shieldaai/agent-guard, -mcp, -scenarios, -executor
and the experimental @shieldaai/agent-map. The code, types and behavior are the same as in
1.1.0. All five packages move to 1.1.1 together, as they always do.

What changed

  • The npm page for the core package now says what problem Agent Guard addresses before
    it says what it does: agents read text they did not write, a hidden instruction can mislead
    them, and the guard limits what a misled agent can do. It links to the
    OWASP Top 10 for Agentic Applications mapping.
  • The core package description on npm leads with that outcome.
  • The repository README points from its problem section to the OWASP table.
  • The release procedure says to publish from a full clone. npm does not record gitHead
    when it publishes from a git worktree checkout, which is why
    @shieldaai/agent-guard@1.1.0 has none.
  • The Python Cartography integration (in the repository, not on npm) locks dnspython
    2.9.2 for GHSA-vvf4-9x63-8xvv.
    None of the npm packages use it.

Upgrading from 1.1.0

Nothing to do. Changing 1.1.0 to 1.1.1 in your dependencies changes no code. Keep all
the packages you use on the same version.

Known limits

The limits of 1.1.0 and 1.0.0 still apply; see also
Support and limits.

Verification

All 19 checks passed on the release candidate 8fd8ab6
(pull request 62, CI run
43506611372): npm run check
on Node 22, 24 and 26 on Linux and on macOS and Windows; the browser checks in Chromium,
Firefox and WebKit; the Neo4j integration tests; the Docker isolation and production-image
checks; the Python dependency audit; CodeQL with no open alerts. CI and CodeQL also passed on
the merge commit 223d865 (CI run
43510071352).

Two CI fixes landed with the approval (pull request 64),
neither in published code: the browser jobs' mirror check accepts GitHub's AWS-hosted runners, whose
first apt mirror is the regional ec2.archive.ubuntu.com archive rather than the Azure one, and a
viewer test now waits for both requests it checks.

Assets 7
Loading